Skip to content

Comments

Merge beta to master#18040

Merged
SaschaCowley merged 3 commits intomasterfrom
beta
May 2, 2025
Merged

Merge beta to master#18040
SaschaCowley merged 3 commits intomasterfrom
beta

Conversation

@SaschaCowley
Copy link
Member

wmhn1872265132 and others added 3 commits April 30, 2025 11:21
Description of user facing changes
Updated the symbols, gestures, character descriptions files for Simplified Chinese.

Description of development approach
Updated the symbols, gestures, character descriptions files for Simplified Chinese.
Closes #17973

Summary of the issue:
Focus handling in the "Connect to another computer" dialog is
suboptimal.

Description of user facing changes
* When connecting using a remote relay server, after a key is generated
by the server, the key field is automatically focused.
* When connecting using a local relay server, after detecting the
external IP, the external IP field is automatically focused.
* When attempting to initiate a connection with a blank host/port and/or
key field, the first erroneously empty field is focused after the error
dialog is dismissed.

Description of development approach
Focusing key/external IP fields:
Since the indeterminate progress dialog is shown asynchronously, we
can't know for certain when the connection dialog will be focusable
again. This is problematic as we can only (successfully) call `SetFocus`
on children of focusable dialogs.
To work around this, bind an event handler to the dialog after
successfully generating a key/detecting the external IP that:

* Is triggered by `wx.EVT_ACTIVATE`, so it fires when the dialog is
focused (as this only happens when the dialog is focusable).
* Focuses the key or external IP field, as appropriate.
* Unbinds itself, so the event is only called the once.

Focusing the first empty control:
Add an `if` statement that selects the appropriate control based on
which one is empty.

Testing strategy:
Attempted to perform a variety of legal and illegal operations with the
dialog.

Known issues with pull request:
None.
Fixes #17985

Summary of the issue:
Muting remote via an input gesture works even if no remote access
session is in progress.

Description of user facing changes
Using an input gesture to mute Remote Access is now disallowed when not
connected.

Description of development approach
Check whether connected in
`_remoteClient.client.RemoteClient.toggleMute`.

Testing strategy:
Tested muting and unmuting when connected and not connected.

Known issues with pull request:
Muting is still allowed when connected as follower, which doesn't seem
to make sense. See #18039.
@SaschaCowley SaschaCowley requested a review from a team as a code owner May 2, 2025 02:34
@SaschaCowley SaschaCowley requested a review from seanbudd May 2, 2025 02:34
@SaschaCowley SaschaCowley merged commit 842f353 into master May 2, 2025
6 of 8 checks passed
@github-actions github-actions bot added this to the 2025.2 milestone May 2, 2025
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.

2 participants