Dialogues not always opening in recent next snapshots on initial run after update #4475
Comments
|
Attachment dialogue vanish.txt added by briang1 on 2014-09-21 12:18 |
|
Comment 2 by briang1 (in reply to comment 1) on 2014-09-21 16:39 It was OK here, Large gap, but its based on what I had. Replying to briang1: |
|
Comment 3 by jteh on 2014-09-24 03:54 I'd say this is almost certainly #3763 (wxPython upgrade). This does fall within the regression window. Unfortunately, it sounds like it's going to be extremely difficult to reproduce reliably. |
|
Comment 5 by briang1 on 2014-09-24 07:19 I |
|
Comment 6 by briang1 (in reply to comment 4) on 2014-09-24 17:49 If you reboot again, then it will once again work. |
|
Comment 7 by nvdakor on 2014-09-24 22:31 |
|
Comment 8 by nvdakor on 2014-09-24 23:31 |
|
Comment 9 by briang1 on 2014-09-25 07:04 |
|
Comment 10 by Michael Curran <mick@... on 2014-09-30 09:47 |
|
Comment 11 by briang1 on 2014-09-30 10:56 I'll await the new snap and see what happens. |
|
Comment 12 by jteh (in reply to comment 11) on 2014-09-30 11:05
It's very unlikely that this fix will fix that problem. That problem is due to Windows not allowing NVDA to become the foreground window, which is a restriction we cannot override in a portable copy or any copy at all on Windows XP. |
|
Comment 14 by briang1 on 2014-10-03 10:48 There have been no problems with the two issues noted on this and the other tickets so far on several machines. Unless anyone else has had problems I think this can be closed as fixed now. |
|
Comment 15 by jteh on 2014-10-03 11:23 |
|
Comment 16 by James Teh <jamie@... on 2015-01-09 02:45 |
…arn't told to hide their first window, when executed with shellExecute. Fixes #4475 Specifically this is core.restart, launching NVDA after installation, and launching the launcher after an update is downloaded. This was always an error, but some how NVDA with WX 2 seemed to get around it. Not so for WX 3.
Reported by briang1 on 2014-09-21 12:16
Note this may be related to the previous ticket, but I have not seen the freezing etc here.
This is a strange one
After any update has been done to an installed copy of next, when one goes via menus, at least the synth menu, and probably others, will not display. Nvda thinks it is open though..
This seems far more likely to occur if there is at least one synth extra in the list, say, pico, or speech Hub etc, but its even more likely if there are a few add ons as well.
That is the best i can do, as a clean install of next did not seem to do it four times I tried, but you cannot really prove a negative.
Certainly an installed copy of Master with quite a few add ons and synths does not do it either, nor any portable create, even over the one running, presumably due to the fact you have to manually run the new copy on a portable create.
It has been observed on XP and 7 so far. The log is not of much use, but I've added one in the downloads anyway. The synth its checking for when it falls out is always the same as in this log, and the fact Speech hub is being a hog here is of no import to the effect.
What is actually happening is that nvda thinks its opened the dialogue, but no amount of alt/tabing can see it. Thus any attempt to open another in the same session will fail with the already open dialogue error. You have to reboot nvda.
Then it works perfectly.
It does not happen on a first boot of the day either, it has to be a direct run from an installed copy update or overwrite to show the issue.
One can wait an hour before asking it to display the dialogue, it still fails to come up.
I had thought that maybe the anti virus was stopping it due to it checking it, hence the above.
So far only two people have confirmed they can get this effect.�
Not really serious, but irritating!
Blocking #3763, #4476, #4492
The text was updated successfully, but these errors were encountered: