Skip to content

fix(ui): the confirmation-depth field sets the depth only inside a room - #337

Merged
corpetty merged 1 commit into
mainfrom
fix/xmr-depth-qml-guard
Oct 21, 2026
Merged

corpetty merged 1 commit into
mainfrom
fix/xmr-depth-qml-guard

Conversation

@corpetty

Copy link
Copy Markdown
Owner

The 0.3.2 release check found a QML TypeError at RoomComposer.qml:838 on Start something, from #333's depth field: the field's initial text set room.splitXmrDepth before a room existed. The field now sets it only when there is a room. The fix is re-checked on the rebuilt AppImage before the release goes out.

🤖 Generated with Claude Code

…de a room

The 0.3.2 AppImage's log had a QML TypeError at RoomComposer.qml:838 on Start
something. The composer exists there before any room does, and the depth field's
initial text fired onTextChanged, which set room.splitXmrDepth on an undefined
room. It now sets it only when there is a room (#333 added the field).

Tested-Behavior: checked on the rebuilt 0.3.2 AppImage under Xvfb — its log had the TypeError at Start something before this change, and the release gate re-runs that check on this commit

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Session-Id: 836705fe-fda9-501b-8ac2-1ce50b5af64a
@corpetty
corpetty merged commit 67e6fd5 into main Oct 21, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant