Date   
Re: Can anyone help with itis oddity?

Brian's Mail list account
 

The only log I can get at is the one in the nvda folder itself.
Traceback (most recent call last):
File "nvda.pyw", line 212, in <module>
File "logHandler.pyo", line 343, in initialize
File "logHandler.pyo", line 221, in __init__
IOError: [Errno 22] invalid mode ('wt') or filename: 'C:\\Users\\Brian\\AppData\\Local\\Temp\\nvda.log'

Brian


bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "Brian's Mail list account via Groups.Io" <bglists=blueyonder.co.uk@groups.io>
To: "NVDA Dev list on groups.io" <nvda-devel@groups.io>
Sent: Thursday, August 22, 2019 2:00 PM
Subject: [nvda-devel] Can anyone help with itis oddity?


I have just returned from trying to run the new Trial version of nvda with the fixed Explorer crash on the computer at our studio. It is running Windows home Premium 64 bit and is all up to date. I had put it on as a temp copy on a ramstick, and tested it on this machine at home,but when I tried to run it on the other machine it clamed that the program nvda.exe was not a valid 32 or 64 bit but in fact a 16bit one and therefore not supported. It did not mention the exe file just the folder name it was in.
I tried copying it over to the main drive with the same result.
Is there any reason why this might happen?
A temp copy of the current stable version works perfectly wherever you run it from.
All suggestions welcome.

Why on earth should it think its was a 16bit? I even ran it from a batch file and the same thing happens but back here on the machine I made it on all is still fine. This is 7 pro though.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

Snapshot page on web site

Brian's Mail list account
 

Now we have migrated Python 3 work to Alpha, is there any need for either of the other two snaps based on Python 3 on the site?
It might be an idea to add one as a link to try builds for solving specific issues, as an easy way for those affected to see if these issues are fixed.
I'm assuming Threshold snaps are now both redundant of course here.

Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

Re: Snapshot page on web site

 

Yes, I agree with you. The threshold has already completed its task.
thank

Re: Snapshot page on web site

Brian's Mail list account
 

Yes at the moment here I have the stable installed the beta and alpha as portable copies and a try build for windows 7 Explorer crashes on a ramstick, plus a copy of the stable I can reinstall if I have any issues. As I say test versions on the page might be easier than making everyone go to a link in the github issue chain.

Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "dingpengyu" <@dingpengyu>
To: <nvda-devel@groups.io>
Sent: Friday, August 23, 2019 9:22 AM
Subject: Re: [nvda-devel] Snapshot page on web site


Yes, I agree with you. The threshold has already completed its task.
thank

Sapi 4 issues in alpha finally killed

Brian's Mail list account
 

At least it looks like the recent update has fixed the crash. Thanks, not that I use it a lot myself.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

Debug Helper 1.0: new add-on released

Luke Davis
 

Good evening:

I wouldn't normally post something like this here, but this add-on is of primary interest to developers, and I know similar functionality has been requested by one or two people in the past.

I am announcing the release of the first stable version of Debug Helper. This is an add-on which is intended to help people who do a lot of work with the NVDA log. If you are trying to report problems with something you're doing, or writing an add-on, or trying to fix something, you may find it useful to be able to jump right to the spot in the log before or after the error occurred, or some important output happened.

At the press of a key (default: nvda+shift+F1), this add-on will insert a "mark line" in the NVDA log, which you can then search for in a text editor. Each mark line includes a sequential number, and can have 1 or more blank lines before/after it to aid in finding it quickly when fast-arrowing.

It is Python 2 and 3 compatible, and works in NVDA versions from 2017.3 through 2019.3.

The add-on will hopefully be on the community site soon, but for now it can be downloaded here: https://github.com/XLTechie/debugHelper/releases/download/1.0/debugHelper-1.0.nvda-addon

Full documentation, including larger usage examples: https://github.com/XLTechie/debugHelper/blob/stable/readme.md

GitHub repo (for issues/to download development versions, etc.):
https://github.com/XLTechie/debugHelper

This is a small add-on with a very specific set of use cases right now, but if you have ideas for ways it could be expanded, please contact me.

Note: I've received two reports that suggest it doesn't always install first time in some old Windows 10 versions. If this happens to you, try to install it once or twice more, which I have been told works (and please send me a log!). No reason is yet known why that might be happening.

Luke

Re: Ref :https://github.com/nvaccess/nvda/pull/10078

derek riemer
 

Yes, it's in master.
FYI, You can tell by looking to see if the PR was merged. Soon after a PR is merged, an automatic build process deploys an alpha snapshot. To see if something was merged, you can check the heading 1 on the page. the line after it says merged.
For example,
Ensure that no reference is kept to sapi4 synth on terminate #10078
is what you want on this PR.


On Mon, Aug 19, 2019 at 2:32 AM Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io> wrote:
https://github.com/nvaccess/nvda/pull/10078

Hi has this made it to the alpha snaps yet?
 I'm not up to speed with how this process  works but on the current alpha
we see a few issues still. 1. it says Yield is deprecated, but later on  it
seems like there is indeed a circular issue that calls itself until
something gives up then windows notices and asks if you want to close it but
of course its stopped speaking so you never here the message!
INFO - updateCheck.AutoUpdateChecker._started (09:04:42.038):
Performing automatic update check
IO - inputCore.InputManager.executeGesture (09:04:45.043):
Input: kb(desktop):NVDA+n
IO - speech.speak (09:04:45.107):
Speaking [LangChangeCommand ('en_GB'), 'NVDA  menu']
IO - inputCore.InputManager.executeGesture (09:04:50.786):
Input: kb(desktop):downArrow
IO - speech.speak (09:04:50.814):
Speaking [LangChangeCommand ('en_GB'), 'Preferences  subMenu  p']
IO - inputCore.InputManager.executeGesture (09:04:52.410):
Input: kb(desktop):rightArrow
IO - speech.speak (09:04:52.438):
Speaking [LangChangeCommand ('en_GB'), 'Settings...  s  1 of 6']
IO - inputCore.InputManager.executeGesture (09:04:53.594):
Input: kb(desktop):enter
DEBUG - gui.settingsDialogs.__new__ (09:04:53.599):
Creating new settings dialog (multiInstanceAllowed:False). State of
_instances {}
DEBUG - windowUtils.getWindowScalingFactor (09:04:53.600):
GetDpiForWindow failed, using GetDeviceCaps instead
DEBUG - windowUtils.getWindowScalingFactor (09:04:53.606):
GetDpiForWindow failed, using GetDeviceCaps instead
IO - speech.speak (09:04:53.690):
Speaking [LangChangeCommand ('en_GB'), 'NVDA Settings: General (normal
configuration)  dialog']
IO - speech.speak (09:04:53.692):
Speaking [LangChangeCommand ('en_GB'), 'Categories:  list']
IO - speech.speak (09:04:53.697):
Speaking [LangChangeCommand ('en_GB'), 'General  1 of 15']
IO - inputCore.InputManager.executeGesture (09:04:55.595):
Input: kb(desktop):downArrow
DEBUG - windowUtils.getWindowScalingFactor (09:04:55.597):
GetDpiForWindow failed, using GetDeviceCaps instead
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:04:55.600):
Setting state to destroyed for instance:
<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 0}
DEBUG - windowUtils.getWindowScalingFactor (09:04:55.603):
GetDpiForWindow failed, using GetDeviceCaps instead
IO - speech.speak (09:04:55.693):
Speaking [LangChangeCommand ('en_GB'), 'Speech  2 of 15']
IO - inputCore.InputManager.executeGesture (09:04:57.603):
Input: kb(desktop):tab
IO - speech.speak (09:04:57.674):
Speaking [LangChangeCommand ('en_GB'), 'Speech  property page']
IO - speech.speak (09:04:57.681):
Speaking [LangChangeCommand ('en_GB'), 'Synthesizer  grouping']
IO - speech.speak (09:04:57.688):
Speaking [LangChangeCommand ('en_GB'), 'Synthesizer  edit  read only  multi
line  Alt+s']
IO - speech.speak (09:04:57.690):
Speaking [LangChangeCommand ('en_GB'), 'eSpeak NG\r']
DEBUGWARNING - Python warning (09:04:57.690):
C:\nvda extra\library.zip\api.py:287: DeprecationWarning: Yield() is
deprecated
IO - inputCore.InputManager.executeGesture (09:04:59.475):
Input: kb(desktop):tab
IO - speech.speak (09:04:59.504):
Speaking [LangChangeCommand ('en_GB'), 'Change...  button  Alt+h']
IO - inputCore.InputManager.executeGesture (09:05:00.627):
Input: kb(desktop):space
IO - speech.speak (09:05:00.631):
Speaking [LangChangeCommand ('en_GB'), 'space', EndUtteranceCommand()]
IO - speech.speak (09:05:00.631):
Speaking [LangChangeCommand ('en_GB'), 'pressed']
DEBUG - gui.settingsDialogs.__new__ (09:05:00.795):
Creating new settings dialog (multiInstanceAllowed:True). State of
_instances {<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>:
1}
DEBUG - windowUtils.getWindowScalingFactor (09:05:00.796):
GetDpiForWindow failed, using GetDeviceCaps instead
DEBUGWARNING - synthDriverHandler.getSynthList (09:05:00.801):
Synthesizer 'oneCore' doesn't pass the check, excluding from list
IO - speech.speak (09:05:00.856):
Speaking [LangChangeCommand ('en_GB'), 'Select Synthesizer  dialog']
IO - speech.speak (09:05:00.862):
Speaking [LangChangeCommand ('en_GB'), 'Synthesizer:  combo box  eSpeak NG
collapsed  Alt+s']
IO - inputCore.InputManager.executeGesture (09:05:04.619):
Input: kb(desktop):downArrow
IO - speech.speak (09:05:04.626):
Speaking [LangChangeCommand ('en_GB'), 'Microsoft Speech API version 4']
IO - inputCore.InputManager.executeGesture (09:05:05.947):
Input: kb(desktop):downArrow
IO - speech.speak (09:05:05.970):
Speaking [LangChangeCommand ('en_GB'), 'Microsoft Speech API version 5']
IO - inputCore.InputManager.executeGesture (09:05:07.947):
Input: kb(desktop):downArrow
IO - speech.speak (09:05:07.969):
Speaking [LangChangeCommand ('en_GB'), 'Microsoft Speech Platform']
IO - inputCore.InputManager.executeGesture (09:05:09.674):
Input: kb(desktop):downArrow
IO - speech.speak (09:05:09.692):
Speaking [LangChangeCommand ('en_GB'), 'No speech']
IO - inputCore.InputManager.executeGesture (09:05:10.762):
Input: kb(desktop):upArrow
IO - speech.speak (09:05:10.771):
Speaking [LangChangeCommand ('en_GB'), 'Microsoft Speech Platform']
IO - inputCore.InputManager.executeGesture (09:05:11.226):
Input: kb(desktop):upArrow
IO - speech.speak (09:05:11.242):
Speaking [LangChangeCommand ('en_GB'), 'Microsoft Speech API version 5']
IO - inputCore.InputManager.executeGesture (09:05:12.395):
Input: kb(desktop):upArrow
IO - speech.speak (09:05:12.412):
Speaking [LangChangeCommand ('en_GB'), 'Microsoft Speech API version 4']
IO - inputCore.InputManager.executeGesture (09:05:16.683):
Input: kb(desktop):enter
DEBUG - speechDictHandler.SpeechDict.load (09:05:16.781):
Loading speech dictionary
'.\userConfig\speechDicts\voiceDicts.v1\sapi4\sapi4-English-American_ Reed
(Adult Male) - ViaVoice Outloud 4.0.dic'...
DEBUG - speechDictHandler.SpeechDict.load (09:05:16.782):
file '.\userConfig\speechDicts\voiceDicts.v1\sapi4\sapi4-English-American_
Reed (Adult Male) - ViaVoice Outloud 4.0.dic' not found.
DEBUG - synthDriverHandler.SynthDriver.loadSettings (09:05:16.782):
Loaded settings for SynthDriver sapi4
INFO - synthDriverHandler.setSynth (09:05:16.782):
Loaded synthDriver sapi4
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:05:16.782):
Setting state to destroyed for instance:
<gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at
0x05D9BCB0>: 0}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:05:16.783):
Setting state to destroyed for instance:
<gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at
0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:05:16.785):
Setting state to destroyed for instance:
<gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at
0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:05:16.786):
Setting state to destroyed for instance:
<gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at
0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:05:16.788):
Setting state to destroyed for instance:
<gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at
0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:05:16.788):
Setting state to destroyed for instance:
<gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at
0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:05:16.789):
Setting state to destroyed for instance:
<gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at
0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:05:16.790):
Setting state to destroyed for instance:
<gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at
0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:05:16.791):
Setting state to destroyed for instance:
<gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at
0x05D9BCB0>: 1}
IO - speech.speak (09:05:16.818):
Speaking [LangChangeCommand ('en_US'), 'NVDA Settings: Speech (normal
configuration)  dialog']
DEBUGWARNING - characterProcessing._getSpeechSymbolsForLocale
(09:05:16.818):
No CLDR data for locale en_US
DEBUGWARNING - synthDrivers.sapi4.SynthDriver.speak (09:05:16.818):
Unsupported speech command: LangChangeCommand ('en_US')
IO - speech.speak (09:05:16.865):
Speaking [LangChangeCommand ('en_US'), 'Speech  property page']
IO - speech.speak (09:05:16.871):
Speaking [LangChangeCommand ('en_US'), 'Synthesizer  grouping']
IO - speech.speak (09:05:16.877):
Speaking [LangChangeCommand ('en_US'), 'Synthesizer  edit  read only  multi
line  Alt+s']
IO - speech.speak (09:05:16.878):
Speaking [LangChangeCommand ('en_US'), 'Microsoft Speech API version 4\r']
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:05:16.884):
Setting state to destroyed for instance:
<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at
0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:05:16.884):
Setting state to destroyed for instance:
<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at
0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:05:16.884):
Setting state to destroyed for instance:
<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at
0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:05:16.885):
Setting state to destroyed for instance:
<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at
0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:05:16.885):
Setting state to destroyed for instance:
<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at
0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:05:16.885):
Setting state to destroyed for instance:
<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at
0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:05:16.885):
Setting state to destroyed for instance:
<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at
0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:05:16.886):
Setting state to destroyed for instance:
<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at
0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:05:16.886):
Setting state to destroyed for instance:
<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at
0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:05:16.886):
Setting state to destroyed for instance:
<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at
0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:05:16.886):
Setting state to destroyed for instance:
<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at
0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:05:16.886):
Setting state to destroyed for instance:
<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at
0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:05:16.887):
Setting state to destroyed for instance:
<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at
0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:05:16.887):
Setting state to destroyed for instance:
<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at
0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:05:16.887):
Setting state to destroyed for instance:
<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at
0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:05:16.887):
Setting state to destroyed for instance:
<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at
0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:05:16.887):
Setting state to destroyed for instance:
<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at
0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:05:16.888):
Setting state to destroyed for instance:
<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at
0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:05:16.888):
Setting state to destroyed for instance:
<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at
0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:05:16.888):
Setting state to destroyed for instance:
<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at
0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:05:16.888):
Setting state to destroyed for instance:
<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at
0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:05:16.888):
Setting state to destroyed for instance:
<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at
0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:05:16.888):
Setting state to destroyed for instance:
<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at
0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:05:16.889):
Setting state to destroyed for instance:
<gui.settingsDialogs.NVDASettingsDialog object at 0x046E3B20>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at
0x05D9BCB0>: 1}
DEBUG - gui.settingsDialogs.SettingsDialog._setInstanceDestroyedState
(09:05:16.923):
Setting state to destroyed for instance:
<gui.settingsDialogs.SynthesizerSelectionDialog object at 0x05D9BCB0>
Current _instances {<gui.settingsDialogs.NVDASettingsDialog object at
0x046E3B20>: 1, <gui.settingsDialogs.SynthesizerSelectionDialog object at
0x05D9BCB0>: 1}
DEBUGWARNING - synthDrivers.sapi4.SynthDriver.speak (09:05:21.520):
Unsupported speech command: LangChangeCommand ('en_US')
IO - inputCore.InputManager.executeGesture (09:05:23.035):
Input: kb(desktop):tab
IO - speech.speak (09:05:23.059):
Speaking [LangChangeCommand ('en_US'), 'Change...  button  Alt+h']
DEBUGWARNING - synthDrivers.sapi4.SynthDriver.speak (09:05:23.060):
Unsupported speech command: LangChangeCommand ('en_US')
IO - inputCore.InputManager.executeGesture (09:05:24.363):
Input: kb(desktop):tab
DEBUGWARNING - synthDrivers.sapi4.SynthDriverBufSink.IUnknown_Release
(09:05:24.380):
ITTSBufNotifySink::Release called too many times by engine
IO - speech.speak (09:05:24.394):
Speaking [LangChangeCommand ('en_US'), 'Voice:  combo box  English-American:
Reed (Adult Male) - ViaVoice Outloud 4.0  collapsed  Alt+v']
DEBUGWARNING - synthDrivers.sapi4.SynthDriver.speak (09:05:24.395):
Unsupported speech command: LangChangeCommand ('en_US')
IO - inputCore.InputManager.executeGesture (09:05:30.315):
Input: kb(desktop):downArrow
DEBUGWARNING - synthDrivers.sapi4.SynthDriverBufSink.IUnknown_Release
(09:05:30.321):
ITTSBufNotifySink::Release called too many times by engine
DEBUGWARNING - synthDrivers.sapi4.SynthDriverBufSink.IUnknown_Release
(09:05:30.325):
ITTSBufNotifySink
::Release called too many times by engine


It has ground to a halt by this time.


NVDA version alpha-18420,a8e8db19
Using Windows version 6.1.7601 service pack 1 workstation


Brian
bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users






--
Derek Riemer
Improving the world one byte at a time!        ⠠⠊⠍⠏⠗⠕⠧⠬ ⠮ ⠸⠺ ⠐⠕ ⠃⠽⠞⠑ ⠁⠞ ⠁ ⠐⠞⠖
•    Accessibility enthusiast.
•    Proud user of the NVDA screen reader.
•    Open source enthusiast.
•    Skier.

•    Personal website: https://derekriemer.com




Monitor page refresh in browser

Beqa Gozalishvili
 

hello.


i am writing some addon and i need to monitor change on webpage when
page reloads.

i can check if something exists, but i can' invoke it when page reloads.

is there some event or something else to be sure that page refreshed
and invoke some part of code?


thanks.

minor Bugfix release of debugHelper #addonrelease

Luke Davis
 

Hello all

After consultation with the three users who reported install problems with debugHelper, I am releasing what I believe to be a bugfix for the problem encountered.

Version 1.0.1 can be found here:
https://github.com/XLTechie/debugHelper/releases/download/v1.0.1/debugHelper-1.0.1.nvda-addon

There were no actual code changes; it works exactly the same as before. The problem was probably an issue of addonHandler, or the installation routine, getting confused by DOS style newlines in the source file, instead of the Unix style it was expecting. That, in combination with messed up ComTypes on a few people's older versions of Windows 10 or 7, caused the problem that was observed. At least, that's what I believe happened.

If anyone has problems with this one, please get in touch!

Readme at: https://github.com/XLTechie/debugHelper/blob/master/readme.md

Luke

Does alpha snap auto update on windows 7?

Brian's Mail list account
 

I raised this a while back but I've been using it all day and never has it prompted for update, so I did a manual check and an update was there. If this had been a beta snap it would have asked by that time.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

Re: Does alpha snap auto update on windows 7?

David Moore
 

Hi!

Even with Windows 10, it sometimes prompts me that a new Alpha snap is there, and sometimes, I have to check.

I just installed the latest alpha snapshot today,

18474, I believe.

I am so glad you can get used to the python three version of NVDA now, to get prepared.

I am really getting used to using the one core voices, for example, instead of the add-on speech package I used before.

Have a great one!

David Moore

                                                                Sent from Mail for Windows 10

 

From: Brian's Mail list account via Groups.Io
Sent: Wednesday, August 28, 2019 3:57 PM
To: NVDA Dev list on groups.io
Subject: [nvda-devel] Does alpha snap auto update on windows 7?

 

I raised this a while back but I've been using it all day and never has it

prompted for update, so I did a manual check and an update was there. If

this had been a beta snap it would have asked by that time.

Brian

 

bglists@...

Sent via blueyonder.

Please address personal E-mail to:-

briang1@..., putting 'Brian Gaff'

in the display name field.

Newsgroup monitored: alt.comp.blind-users

 

 

 

 

Re: Does alpha snap auto update on windows 7?

Luke Davis
 

On Wed, 28 Aug 2019, Brian's Mail list account via Groups.Io wrote:

I raised this a while back but I've been using it all day and never has it prompted for update, so I did a manual check and an update was there. If this had been a beta snap it would have asked by that time.
I can confirm the identical behavior in Windows 10 1903, with a portable copy.

--
Luke Davis
Moderator: the new NVDA Help mailing list (NVDAHelp+subscribe@groups.io)
Author: Debug Helper NVDA add-on (https://github.com/XLTechie/debugHelper)

Re: Does alpha snap auto update on windows 7?

Brian's Mail list account
 

I'm on windows 7, but I do not like real sounding voices for screenreader use for menus etc, but luckily I can still use Espeak Quincy and only use real voices if I need to read a long document.
I guess its what you are used to.

However getting back on topic. There is definitely something flaky about auto checking for updates on the Python 3 snaps compared to the others.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "David Moore" <jesusloves1966@...>
To: <nvda-devel@groups.io>
Sent: Wednesday, August 28, 2019 9:34 PM
Subject: Re: [nvda-devel] Does alpha snap auto update on windows 7?


Hi!
Even with Windows 10, it sometimes prompts me that a new Alpha snap is there, and sometimes, I have to check.
I just installed the latest alpha snapshot today,
18474, I believe.
I am so glad you can get used to the python three version of NVDA now, to get prepared.
I am really getting used to using the one core voices, for example, instead of the add-on speech package I used before.
Have a great one!
David Moore
Sent from Mail for Windows 10

From: Brian's Mail list account via Groups.Io
Sent: Wednesday, August 28, 2019 3:57 PM
To: NVDA Dev list on groups.io
Subject: [nvda-devel] Does alpha snap auto update on windows 7?

I raised this a while back but I've been using it all day and never has it
prompted for update, so I did a manual check and an update was there. If
this had been a beta snap it would have asked by that time.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

Re: Does alpha snap auto update on windows 7?

Brian's Mail list account
 

Also I see the update check say its initialised, but I never see any log entries for it.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "David Moore" <jesusloves1966@...>
To: <nvda-devel@groups.io>
Sent: Wednesday, August 28, 2019 9:34 PM
Subject: Re: [nvda-devel] Does alpha snap auto update on windows 7?


Hi!
Even with Windows 10, it sometimes prompts me that a new Alpha snap is there, and sometimes, I have to check.
I just installed the latest alpha snapshot today,
18474, I believe.
I am so glad you can get used to the python three version of NVDA now, to get prepared.
I am really getting used to using the one core voices, for example, instead of the add-on speech package I used before.
Have a great one!
David Moore
Sent from Mail for Windows 10

From: Brian's Mail list account via Groups.Io
Sent: Wednesday, August 28, 2019 3:57 PM
To: NVDA Dev list on groups.io
Subject: [nvda-devel] Does alpha snap auto update on windows 7?

I raised this a while back but I've been using it all day and never has it
prompted for update, so I did a manual check and an update was there. If
this had been a beta snap it would have asked by that time.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

Re: Does alpha snap auto update on windows 7?

 

Could you guys please provide the output of the following in a python console?

import updateCheck; print(updateCheck.state)


My output is as follows:

{'pendingUpdateAPIVersion': (0, 0, 0), 'pendingUpdateBackCompatToAPIVersion': (0, 0, 0), 'dontRemindVersion': '2019.2', 'lastCheck': 1567002250.28, 'pendingUpdateFile': None, 'pendingUpdateVersion': None}

Regards,

Leonard

Op 29-8-2019 om 09:11 schreef Brian's Mail list account via Groups.Io:

Also I see the update check say its initialised, but I never see any log entries for it.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users
----- Original Message ----- From: "David Moore" <jesusloves1966@...>
To: <nvda-devel@groups.io>
Sent: Wednesday, August 28, 2019 9:34 PM
Subject: Re: [nvda-devel] Does alpha snap auto update on windows 7?


Hi!
Even with Windows 10, it sometimes prompts me that a new Alpha snap is there, and sometimes, I have to check.
I just installed the latest alpha snapshot today,
18474, I believe.
I am so glad you can get used to the python three version of NVDA now, to get prepared.
I am really getting used to using the one core voices, for example, instead of the add-on speech package I used before.
Have a great one!
David Moore
Sent from Mail for Windows 10

From: Brian's Mail list account via Groups.Io
Sent: Wednesday, August 28, 2019 3:57 PM
To: NVDA Dev list on groups.io
Subject: [nvda-devel] Does alpha snap auto update on windows 7?

I raised this a while back but I've been using it all day and never has it
prompted for update, so I did a manual check and an update was there. If
this had been a beta snap it would have asked by that time.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users












And finally, for now.

Brian's Mail list account
 

On the log produced by the python 3 snapshot we have some log entries near the start which are odd.
DEBUG - windowUtils._rawWindowProc (08:00:49.894):
CustomWindow rawWindowProc called for unknown window 262472
DEBUG - windowUtils._rawWindowProc (08:00:49.894):
CustomWindow rawWindowProc called for unknown window 262472
DEBUG - windowUtils._rawWindowProc (08:00:49.894):
CustomWindow rawWindowProc called for unknown window 262472
DEBUG - windowUtils._rawWindowProc (08:00:49.895):
CustomWindow rawWindowProc called for unknown window 262472
DEBUG - core.main (08:00:49.897):
etc.
JUst wondered what they were.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

Re: And finally, for now.

 

They have been introduced by the vision framework, I added some additional debug statements to the window creation there. Nothing to worry about. These issues were already there, they just weren't logged.

Re: Does alpha snap auto update on windows 7?

ChrisLM
 

Hi, this is an output on Windows version 6.1.7601 service pack 1 workstation with NVDA alpha-18474,2a130565:

{'pendingUpdateAPIVersion': (0, 0, 0), 'pendingUpdateVersionTuple': None, 'dontRemindVersion': 'alpha-18474,2a130565', 'lastCheck': 1567065986.9906137, 'pendingUpdateFile': None, 'pendingUpdateVersion': None, 'pendingUpdateBackCompatToAPIVersion': (0, 0, 0)}


Chris.

In reply to Leonard de Ruijter, 29/08/2019 09:13:

Could you guys please provide the output of the following in a python
console?

import updateCheck; print(updateCheck.state)

Re: And finally, for now.

Brian's Mail list account
 

OK then what about this little problem on another windows 7 machine?



Hi folks. I just installed the 3 try version of nvda to stop the explorer crash in windows 7, and of course its too early to tell the outcome of that. However when Windows 7 Home Premium boots up it firstly takes a long time, 11 seconds according to the log, even though the same settings and add ons here at home do not have any issues. Here are the parts of the log that look like issues.

Initializing UIA support
DEBUGWARNING - RPC process 1824 (dwm.exe) (13:01:53.380):
Thread 3364, build\x86_64\remote\injection.cpp, inproc_winEventCallback, 66:
SetWindowsHookEx with WH_GETMESSAGE failed, GetLastError returned 5

DEBUGWARNING - RPC process 1824 (dwm.exe) (13:01:53.381):
Thread 3364, build\x86_64\remote\injection.cpp, inproc_winEventCallback, 69:
SetWindowsHookEx with WH_CALLWNDPROC failed, GetLastError returned 5

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (13:01:53.629):
UIAutomation: IUIAutomation
DEBUG - core.main (13:01:55.351):

snip
NVDA initialized
DEBUG - core.main (13:01:58.660):
entering wx application main loop
DEBUGWARNING - watchdog._watcher (13:01:59.332):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 221, in <module>
File "core.pyc", line 536, in main
File "wx\core.pyc", line 2134, in MainLoop
File "gui\__init__.pyc", line 997, in Notify
File "core.pyc", line 505, in run
File "IAccessibleHandler.pyc", line 901, in pumpAll
File "IAccessibleHandler.pyc", line 624, in processGenericWinEvent
File "IAccessibleHandler.pyc", line 532, in winEventToNVDAEvent
File "NVDAObjects\IAccessible\__init__.pyc", line 42, in getNVDAObjectFromEvent
File "IAccessibleHandler.pyc", line 342, in accessibleObjectFromEvent
File "oleacc.pyc", line 265, in AccessibleObjectFromEvent

DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (13:01:59.472):
accRole failed: (-2147024809, 'The parameter is incorrect.', (None, None, None, 0, None))
IO - speech.speak (13:01:59.529):
Speaking [LangChangeCommand ('en_GB'), 'NVDA']
IO - inputCore.InputManager.executeGesture (13:02:07.047):
Input: kb(desktop):upArrow
IO - inputCore.InputManager.executeGesture (13:02:07.431):
Input: kb(desktop):downArrow
IO - inputCore.InputManager.executeGesture (13:02:07.767):
Input: kb(desktop):upArrow
IO - inputCore.InputManager.executeGesture (13:02:08.023):
Input: kb(desktop):downArrow
IO - inputCore.InputManager.executeGesture (13:02:08.279):
Input: kb(desktop):upArrow
IO - inputCore.InputManager.executeGesture (13:02:11.087):
Input: kb(desktop):downArrow
IO - inputCore.InputManager.executeGesture (13:02:11.439):
Input: kb(desktop):upArrow
IO - inputCore.InputManager.executeGesture (13:02:11.734):
Input: kb(desktop):downArrow
IO - inputCore.InputManager.executeGesture (13:02:13.415):
Input: kb(desktop):alt+tab
IO - speech.speak (13:02:13.900):
Speaking [LangChangeCommand ('en_GB'), 'Desktop icon 2 of 2']
IO - speech.speak (13:02:14.174):
Speaking [LangChangeCommand ('en_GB'), 'FolderView list']

As you will note we have the guest appearence of a very old problem from the past, a blank nvda window focussed after boot up of the machine. If I then reboot nvda things seem to work as normal.
Is this a problem that anyone else has had, could it be a windows issue??
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "Leonard de Ruijter" <@leonardder>
To: <nvda-devel@groups.io>
Sent: Thursday, August 29, 2019 8:23 AM
Subject: Re: [nvda-devel] And finally, for now.


They have been introduced by the vision framework, I added some
additional debug statements to the window creation there. Nothing to
worry about. These issues were already there, they just weren't logged.


Recommended way of "hiding" certain elements #3030-advice

Toni Barth
 

Hello NVDA Developers,
 
i'm developing an add-on right now to enhance the usability of an application. This application contains at least one table with several cells, but some of those cells, even though they are navigatable by NVDA, contain unimportant information, like the text 'None' or just an icon. I thus wanted to "hide" those cells for the user and tried several ways to do so. I overlayed the table row and override _get_children(), removing the certain children from the list, but I noticed that _get_children() never seems to get executed. I also tried adding states to the specific cells like controlTypes.STATE_INVISIBLE or controlTypes.STATE_UNAVAILABLE, but nothing helped. I also tried moving the focus manually whenever the cell is focused by using event_gainFocus(), but even this seems to mess up things even further.
 
Do you have an idea how to remove those cells from keyboard navigation (not navigator, but at least from tab/arrow keys navigation)?
 
Thanks for your help :).
 
Best Regards.
 
Toni Barth