Comment 1 by jteh on 2015-02-13 20:52
Confirmed. Terrific! Looks like another regression probably caused by wxPython 3. Does not occur in NVDA 2014.4. :(

Comment 2 by JamaicanUser on 2015-04-27 13:58
will the next release of wx python address this issue? it moves to the filter by edit box in the latest version of NVDA using the input gestures dialog.

Comment 3 by bhavyashah on 2015-04-27 18:06
Hi,
This is a rather annoying issue to me as well which I was meaning to report, but, glad to read that a ticket is already in existence reporting the same issue.
I especially keep the Voice Settings dialog open all the while and constantly change my variants and volume aaccording to my background noise since I haven't yet discovered a provision by Windows to quickly turn up or down the volume (instead of keeping the Volume Mixer dialog open always, which due to unknown reasons, I dislike).
If others find this a significant enough issue, I would ask for this issue to be prioritized, for 2015.53, if possible.
Thanks.

Comment 5 by leonarddr (in reply to comment 3) on 2015-07-08 11:29
Replying to bhavyashah:

I especially keep the Voice Settings dialog open all the while and constantly change my variants and volume aaccording to my background noise since I haven't yet discovered a provision by Windows to quickly turn up or down the volume (instead of keeping the Volume Mixer dialog open always, which due to unknown reasons, I dislike).

You can use the synth settings ring for this. The issue is still annoying though. Any idea how we could fix this?

Comment 6 by bhavyashah on 2015-07-08 13:19
Hi,
I cannot use the Synth Settings Ring on my laptop since my laptop's keyboard does not accept four key combinations.
Thanks.

Comment 7 by leonarddr (in reply to comment 6) on 2015-07-08 13:45
Replying to bhavyashah:

I cannot use the Synth Settings Ring on my laptop since my laptop's keyboard does not accept four key combinations.

You can reassign the synth settings ring keys to use three key combinations. But, for further discussion of this, we better take this to the mailing list.

Comment 8 by jteh on 2015-07-09 00:17
Okay. I've finally managed to figure out some stuff here.

It seems that in wxPython 3, if the parent frame is not shown (as is the case with NVDA), focus always gets bounced back to the first control in a dialog. If the parent frame is shown, this doesn't occur. This was not the case in wxPython 2, which is why this didn't show up until NVDA 2015.1.

Unfortunately, we really don't want that parent frame to be visible, but we do want a parent frame so managing children, coming to the foreground, etc. is simpler. The question is whether we can either work around this behaviour or make the parent frame logically visible without being physically visible, if that makes sense. The latter will require quite a bit of sighted assistance.

It seems this issue still occurs in the WX Python 4 snapshots (#7077).

@feerrenrut, Would this be something you are able too look into? Especially in the document formatting dialog, this bug is very annoying.

cc @josephsl

It's certainly annoying, but I don't feel it has higher priority than p2 issues which generally prevent access to something. Particularly in the Document Formatting dialog, those who need extremely efficient access can use the many available accelerators. Fixing this is also likely to be pretty costly in terms of time and potential regressions; see my comment above for details.

This is a friendly reminder for @feerrenrut to please respond to @LeonarddeR's #4918 (comment) by sharing whether it would be possible, as one of our only fully sighted developers of NVDA as well as one who has worked on NVDA's GUI extensively in the past, to look into this issue.

Sorry, I didn't comment on this because I agree with jcsteh, P3 is appropriate. I'll be happy to look at this when we can, this will likely require a fair bit of research into wxPython to work out the best fix. Given that moving to wxPython 4 is on the horizon, it may be best to fix this against wxPython 4 since the rules will likely change.

Note that the behavior in the new NVDA settings dialog introduced in NVDA 2018.2 differs in such a way that the focus now ends up at the first control of a settings panel.

The behavior described in #4918 (comment) is still reproducible after migrating to wxPython 4.

On my side, the issue is fixed in NVDA 2021.2rc1.
If I remember well, I think it has been fixed in NVDA 2021.1 during the transition to WxPython 4.1.1.

@LeonarddeR could you confirm and close?

I confirm I can reproduce with 2020.4 but no longer with 2021.1
Thanks @CyrilleB79 for pointing this out.