Date   

The error sound

Brian's Mail list account <bglists@...>
 

"C:\Program Files (x86)\NVDA\waves\error.wav"

This is where the error file sound is in an installed version of nvda.
it is relatively easy to rename this file to, say error1.wav and add your own file here as error.wav.
Indeed you can use a sound editor to make it quieter then copy it back if you like. However, keep a copy of your altered error.wav as every time you update the snapshot it will put it back to default.
So go ahead, the world is your lobster!
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.


Re: nvda_snapshot_alpha or beta

Brian's Mail list account <bglists@...>
 

The point is though, if you use snaps, then you need to ask yourselves why? Ideally to find problems and report them.
if this is not what you want to do then fine, use the stable. if on the other hand you do need a new feature now, I'm sure one might be able to find a work around for the ding, but I tend to just ignore it if its in a context I've had for ages and reported already, and its been declared benign.

Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Kwork" <istherelife@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Friday, August 17, 2018 5:23 AM
Subject: Re: [nvda] nvda_snapshot_alpha or beta


That ding drives me crazy, and is actually a reason I quit using betas. Having to wait just a bit longer for a new or fixed feature for me is a fair trade off for not having to deal with unquenchable dings. If there was an on/off checkbox, that would become moot. Personal preference only
Travis
----- Original Message -----
From: Quentin Christensen
To: nvda@nvda.groups.io
Sent: Thursday, August 16, 2018 8:04 PM
Subject: Re: [nvda] nvda_snapshot_alpha or beta


Hi Don,


As Joseph mentioned, the "ding" indicates that NVDA encountered an error which it wrote to its log. It doesn't necessarily mean that you can't do whatever you were trying to do - often NVDA itself hits the error, then used a workaround, so from a user point of view, everything may still work normally. The only difference is that in the alpha and beta builds, you get a ding, whereas in the stable release you don't and the error just writes quietly to the log.


The idea is that developers can use it to find when errors are being generated when they are working on something.


There is currently no setting to disable this, however if you are encountering a particular error that you can share how to replicate, do please report it so that we can endeavour to resolve it.


Kind regards


Quentin.


On Fri, Aug 17, 2018 at 12:17 PM, Don H <lmddh50@adams.net> wrote:

Don't know when there is a bug in the alpha or beta versions of NVDA. When running either the Alpha or Beta versions I get a lot of error dings as I call them when browsing using Google Chrome. For example every time i get to a edit box I get the error ding. Sometimes just opening a web site gives me a ding. Is there some reasoning behind such dings?










--

Quentin Christensen
Training and Support Manager


Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/


www.nvaccess.org

Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess


Re: nvda_snapshot_alpha or beta

Brian's Mail list account <bglists@...>
 

What about shoving a silent wav into the folder called the error.wav?
Ok not a good idea as you really do want to report errors, but I was just mentioning a possible work around. In the dev list the other day, in response to Micks question about errors in edit boxes I published some log fragments showing the errors generated in the beta branch during explorer file search. I have seen no reply, but since nothing bad actually happened I'd suggest that the errors are mostly benign, but could be a good way to track down some based on them which might be more serious.


I think people should perhaps think this way.
Did these errors cause a real issue?
If yes then go to gather and start a new issue. If its just another version of an existing one, somebody will come along and see that and probably add it to the old issue and close the new one.
If it does not give any problems to the usage, then it can be just ignored. it can as the poster said, though be annoying if every keystroke generates the noise.
This also happens in Word sometimes, mainly spellchecking, but the error is quite obviously merely the triggering of the error that does not matter at all.
If you really do want to help find bugs then you do need to live with errors. maybe the error sound could be a little quieter?
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Friday, August 17, 2018 3:18 AM
Subject: Re: [nvda] nvda_snapshot_alpha or beta


Hi,
This "ding" sound indicates an error that NVDA has encountered. You can't really turn this off in development snapshots (alpha and beta).
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Don H
Sent: Thursday, August 16, 2018 7:17 PM
To: nvda@nvda.groups.io
Subject: [nvda] nvda_snapshot_alpha or beta

Don't know when there is a bug in the alpha or beta versions of NVDA.
When running either the Alpha or Beta versions I get a lot of error dings as I call them when browsing using Google Chrome. For example every time i get to a edit box I get the error ding. Sometimes just opening a web site gives me a ding. Is there some reasoning behind such dings?


Re: Am Able to Reproduce Issue with Purchasing Kindle Books

Antony Stone
 

Surely a virtual Kindle can log on to the Amazon cloud storage service just
the same as a physical one can?

All the "send to my Kindle" button does it to put the item into your cloud
storage account, for the eBook device (real or virtual) to download next time
it syncs.

Antony.

On Friday 17 August 2018 at 10:53:43, Brian's Mail list account via Groups.Io
wrote:

A lot of people only have a virtual Kindle though, so that would not seem
logical, how would it know where to send it. I am hearing this issue might
be wider than just books to the kindle though, even normal purchases might
be affected. My guess is that something is screwed in the page mark up for
landmarks and headings.
Brian

----- Original Message -----
From: "Gene" <gsasner@ripco.com>
To: <nvda@nvda.groups.io>
Sent: Friday, August 17, 2018 1:03 AM
Subject: Re: [nvda] Am Able to Reproduce Issue with Purchasing Kindle Books


I almost never purchase anything from Amazon but there is a button when you
purchase a Kindle version of a book that says somethin like send to my
Kindle. I don't know if this will do what people want. But those
interested can try the button and see what happens.

Gene
----- Original Message -----

From: Abbie Taylor
Sent: Thursday, August 16, 2018 6:55 PM
To: NVDA List
Subject: [nvda] Am Able to Reproduce Issue with Purchasing Kindle Books


A while back, someone posted here that they were having trouble
purchasing Kindle books on the Amazon site with NVDA. I just tried to
purchase a book, and I couldn't find either the buy with one click
button or the add to cart button. After trying this with both Firefox
and Chrome with similar results, I called their disability hot line. The
representative I talked to was able to add the book to my cart, and I
was able to purchase it that way. I explained to her that others with
visual impairments who use screen reading software are also having
difficulty, and she said she would pass it along. Will just have to see
what happens.
--
#define SIX 1+5
#define NINE 8+1

int main() {
printf("%d\n", SIX * NINE);
}
- thanks to ECB for bringing this to my attention

Please reply to the list;
please *don't* CC me.


Re: Am Able to Reproduce Issue with Purchasing Kindle Books

Brian's Mail list account <bglists@...>
 

A lot of people only have a virtual Kindle though, so that would not seem logical, how would it know where to send it. I am hearing this issue might be wider than just books to the kindle though, even normal purchases might be affected. My guess is that something is screwed in the page mark up for landmarks and headings.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Gene" <gsasner@ripco.com>
To: <nvda@nvda.groups.io>
Sent: Friday, August 17, 2018 1:03 AM
Subject: Re: [nvda] Am Able to Reproduce Issue with Purchasing Kindle Books


I almost never purchase anything from Amazon but there is a button when you purchase a Kindle version of a book that says somethin like send to my Kindle. I don't know if this will do what people want. But those interested can try the button and see what happens.

Gene
----- Original Message -----

From: Abbie Taylor
Sent: Thursday, August 16, 2018 6:55 PM
To: NVDA List
Subject: [nvda] Am Able to Reproduce Issue with Purchasing Kindle Books


A while back, someone posted here that they were having trouble
purchasing Kindle books on the Amazon site with NVDA. I just tried to
purchase a book, and I couldn't find either the buy with one click
button or the add to cart button. After trying this with both Firefox
and Chrome with similar results, I called their disability hot line. The
representative I talked to was able to add the book to my cart, and I
was able to purchase it that way. I explained to her that others with
visual impairments who use screen reading software are also having
difficulty, and she said she would pass it along. Will just have to see
what happens.


--
Abbie Johnson Taylor, Author http://abbiescorner.wordpress.com
http://www.abbiejohnsontaylor.com abbietaylor945@gmail.com Order my new
memoir at http://www.abbiejohnsontaylor.com/memoir.htm


--
Abbie Johnson Taylor, Author
http://www.abbiejohnsontaylor.com
http://abbiescorner.wordpress.com
abbietaylor945@gmail.com


Re: Mozilla fire fox crashes with nvda 2018.3 beta 2

Bobby Vinton <vinton.bobby5277@...>
 

Well can you please let me know because I only have 3 gigs of ram and a 120 ssd drive

On 8/17/2018 12:29 AM, The Wolf wrote:
how can I turn off the multi process feature?


On 8/16/2018 8:36 PM, zahra wrote:
hi.
i never used beta versions of nvda, but i found a solution for
stopping crashing for newer versions of firefox, (firefox quantum).
the solution is disabling multiprocess in firefox.
if someone wish to do this, because of crashing or slowness of the
system, and someone has not powerful system to handel multiprocess
without problem, let me know and i explane how to disable this
horrible feature of firefox quantum!

On 8/17/18, hurrikennyandopo ... <hurrikennyandopo@hotmail.com> wrote:
Hi


If you are referring to nvda in the beta version there is no add ons. if
it is the browser it is the same add ons that are used with the alfa and
stable version and it or those versions do not have the problem only the
beta. It is sorta randam but seems if you use the alfa first then turn
it off then start the beta it will happen then at times.


Gene nz



On 8/16/2018 9:12 PM, Brian's Mail list account via Groups.Io wrote:
Do you use any add ons?
Try disabling them all and then turn them on one at a time if it fixes
it.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "hurrikennyandopo ..."
<hurrikennyandopo@hotmail.com>
To: <nvda@nvda.groups.io>
Sent: Thursday, August 16, 2018 9:35 AM
Subject: Re: [nvda] Mozilla fire fox crashes with nvda 2018.3 beta 2


It seems to happen if i use the alfa snap shot first say to update then
after i turn it off then check with the beta version it seems to crash
but not all the time some times it will just give the message no updates
then you can close it then other times the browser crashes.

this is only with nvda 2018.3 beta 2 not the alfa snap shot.


Gene nz



On 8/16/2018 8:24 PM, hurrikennyandopo ... wrote:
Hi guys


I do not get this problem with the alfa snapshot when i go to do the
following. help then check for update.

it will download the alfa snap shot then let me set it up.


when i go to do the same with the nvda 2018.3 beta 2 snap shot it goes
to open the browser then crashes and then i get the following.


I thought it might of been a corrupted beta etc so totally removed it
all settings etc then reinstalled it. Even done this with a new fresh
copy as well.


INFO - __main__ (20:09:35.987):
Starting NVDA
INFO - core.main (20:09:36.563):
Config dir: C:\nvda beta snapshots\userConfig
INFO - config.ConfigManager._loadConfig (20:09:36.565):
Loading config: .\userConfig\nvda.ini
INFO - core.main (20:09:36.717):
NVDA version 2018.3beta2
INFO - core.main (20:09:36.717):
Using Windows version 10.0.17134 workstation
INFO - core.main (20:09:36.719):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17)
[MSC v.1500 32 bit (Intel)]
INFO - core.main (20:09:36.719):
Using comtypes version 1.1.3
INFO - synthDriverHandler.setSynth (20:09:38.078):
Loaded synthDriver oneCore
INFO - core.main (20:09:38.079):
Using wx version 3.0.2.0 msw (classic)
INFO - brailleInput.initialize (20:09:38.085):
Braille input initialized
INFO - braille.initialize (20:09:38.085):
Using liblouis version 3.6.0
INFO - braille.BrailleHandler.setDisplayByName (20:09:38.088):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (20:09:38.415):
UIAutomation: IUIAutomation5
INFO - core.main (20:09:38.915):
NVDA initialized
INFO - updateCheck.AutoUpdateChecker._started (20:09:38.993):
Performing automatic update check
ERROR - virtualBuffers.VirtualBuffer._loadBuffer (20:10:21.470):
Traceback (most recent call last):
   File "virtualBuffers\__init__.pyo", line 417, in _loadBuffer
WindowsError: [Error 1726] The remote procedure call failed
ERROR - virtualBuffers.VirtualBuffer._loadBuffer (20:11:19.418):
Traceback (most recent call last):
   File "virtualBuffers\__init__.pyo", line 417, in _loadBuffer
WindowsError: [Error 1726] The remote procedure call failed
INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo
(20:12:05.006):
Developer info for navigator object:
name: u'Tell Mozilla about this crash so they can fix it'
role: ROLE_CHECKBOX
states: STATE_CHECKED, STATE_FOCUSABLE, STATE_FOCUSED
isFocusable: True
hasFocus: True
Python object: <NVDAObjects.IAccessible.IAccessible object at
0x035D3450>
Python class mro: (<class 'NVDAObjects.IAccessible.IAccessible'>,
<class
'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class
'documentBase.TextContainerObject'>, <class
'baseObject.ScriptableObject'>, <class
'baseObject.AutoPropertyObject'>,
<type 'object'>)
description: None
location: (477, 450, 355, 16)
value: None
appModule: <'appModuleHandler' (appName u'crashreporter', process ID
9028) at address 5872650>
appModule.productName: u'Firefox'
appModule.productVersion: u'61.0.2'
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 263040
windowClassName: u'Button'
windowControlID: 1007
windowStyle: 1342242819
windowThreadID: 6616
windowText: u'Tell Mozilla about this crash so they can fix it'
displayText: u'Tell Mozilla about this crash so they can fix it'
IAccessibleObject: <POINTER(IAccessible) ptr=0x754280 at 583df30>
IAccessibleChildID: 0
IAccessible event parameters: windowHandle=263040, objectID=-4,
childID=0
IAccessible accName: u'Tell Mozilla about this crash so they can fix
it'
IAccessible accRole: ROLE_SYSTEM_CHECKBUTTON
IAccessible accState: STATE_SYSTEM_CHECKED, STATE_SYSTEM_FOCUSED,
STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1048596)
IAccessible accDescription: None
IAccessible accValue: None




n









Re: Mozilla fire fox crashes with nvda 2018.3 beta 2

 

how can I turn off the multi process feature?

On 8/16/2018 8:36 PM, zahra wrote:
hi.
i never used beta versions of nvda, but i found a solution for
stopping crashing for newer versions of firefox, (firefox quantum).
the solution is disabling multiprocess in firefox.
if someone wish to do this, because of crashing or slowness of the
system, and someone has not powerful system to handel multiprocess
without problem, let me know and i explane how to disable this
horrible feature of firefox quantum!

On 8/17/18, hurrikennyandopo ... <hurrikennyandopo@hotmail.com> wrote:
Hi


If you are referring to nvda in the beta version there is no add ons. if
it is the browser it is the same add ons that are used with the alfa and
stable version and it or those versions do not have the problem only the
beta. It is sorta randam but seems if you use the alfa first then turn
it off then start the beta it will happen then at times.


Gene nz



On 8/16/2018 9:12 PM, Brian's Mail list account via Groups.Io wrote:
Do you use any add ons?
Try disabling them all and then turn them on one at a time if it fixes
it.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "hurrikennyandopo ..."
<hurrikennyandopo@hotmail.com>
To: <nvda@nvda.groups.io>
Sent: Thursday, August 16, 2018 9:35 AM
Subject: Re: [nvda] Mozilla fire fox crashes with nvda 2018.3 beta 2


It seems to happen if i use the alfa snap shot first say to update then
after i turn it off then check with the beta version it seems to crash
but not all the time some times it will just give the message no updates
then you can close it then other times the browser crashes.

this is only with nvda 2018.3 beta 2 not the alfa snap shot.


Gene nz



On 8/16/2018 8:24 PM, hurrikennyandopo ... wrote:
Hi guys


I do not get this problem with the alfa snapshot when i go to do the
following. help then check for update.

it will download the alfa snap shot then let me set it up.


when i go to do the same with the nvda 2018.3 beta 2 snap shot it goes
to open the browser then crashes and then i get the following.


I thought it might of been a corrupted beta etc so totally removed it
all settings etc then reinstalled it. Even done this with a new fresh
copy as well.


INFO - __main__ (20:09:35.987):
Starting NVDA
INFO - core.main (20:09:36.563):
Config dir: C:\nvda beta snapshots\userConfig
INFO - config.ConfigManager._loadConfig (20:09:36.565):
Loading config: .\userConfig\nvda.ini
INFO - core.main (20:09:36.717):
NVDA version 2018.3beta2
INFO - core.main (20:09:36.717):
Using Windows version 10.0.17134 workstation
INFO - core.main (20:09:36.719):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17)
[MSC v.1500 32 bit (Intel)]
INFO - core.main (20:09:36.719):
Using comtypes version 1.1.3
INFO - synthDriverHandler.setSynth (20:09:38.078):
Loaded synthDriver oneCore
INFO - core.main (20:09:38.079):
Using wx version 3.0.2.0 msw (classic)
INFO - brailleInput.initialize (20:09:38.085):
Braille input initialized
INFO - braille.initialize (20:09:38.085):
Using liblouis version 3.6.0
INFO - braille.BrailleHandler.setDisplayByName (20:09:38.088):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (20:09:38.415):
UIAutomation: IUIAutomation5
INFO - core.main (20:09:38.915):
NVDA initialized
INFO - updateCheck.AutoUpdateChecker._started (20:09:38.993):
Performing automatic update check
ERROR - virtualBuffers.VirtualBuffer._loadBuffer (20:10:21.470):
Traceback (most recent call last):
  File "virtualBuffers\__init__.pyo", line 417, in _loadBuffer
WindowsError: [Error 1726] The remote procedure call failed
ERROR - virtualBuffers.VirtualBuffer._loadBuffer (20:11:19.418):
Traceback (most recent call last):
  File "virtualBuffers\__init__.pyo", line 417, in _loadBuffer
WindowsError: [Error 1726] The remote procedure call failed
INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo
(20:12:05.006):
Developer info for navigator object:
name: u'Tell Mozilla about this crash so they can fix it'
role: ROLE_CHECKBOX
states: STATE_CHECKED, STATE_FOCUSABLE, STATE_FOCUSED
isFocusable: True
hasFocus: True
Python object: <NVDAObjects.IAccessible.IAccessible object at
0x035D3450>
Python class mro: (<class 'NVDAObjects.IAccessible.IAccessible'>,
<class
'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class
'documentBase.TextContainerObject'>, <class
'baseObject.ScriptableObject'>, <class
'baseObject.AutoPropertyObject'>,
<type 'object'>)
description: None
location: (477, 450, 355, 16)
value: None
appModule: <'appModuleHandler' (appName u'crashreporter', process ID
9028) at address 5872650>
appModule.productName: u'Firefox'
appModule.productVersion: u'61.0.2'
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 263040
windowClassName: u'Button'
windowControlID: 1007
windowStyle: 1342242819
windowThreadID: 6616
windowText: u'Tell Mozilla about this crash so they can fix it'
displayText: u'Tell Mozilla about this crash so they can fix it'
IAccessibleObject: <POINTER(IAccessible) ptr=0x754280 at 583df30>
IAccessibleChildID: 0
IAccessible event parameters: windowHandle=263040, objectID=-4,
childID=0
IAccessible accName: u'Tell Mozilla about this crash so they can fix
it'
IAccessible accRole: ROLE_SYSTEM_CHECKBUTTON
IAccessible accState: STATE_SYSTEM_CHECKED, STATE_SYSTEM_FOCUSED,
STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1048596)
IAccessible accDescription: None
IAccessible accValue: None




n








--
check out my song on youtube
https://youtu.be/YeWgx2LRu7Y


Re: nvda_snapshot_alpha or beta

Kwork
 


That ding drives me crazy, and is actually a reason I quit using betas. Having to wait just a bit longer for a new or fixed feature for me is a fair trade off for not having to deal with unquenchable dings. If there was an on/off checkbox, that would become moot. Personal preference only
Travis

----- Original Message -----
Sent: Thursday, August 16, 2018 8:04 PM
Subject: Re: [nvda] nvda_snapshot_alpha or beta

Hi Don,

As Joseph mentioned, the "ding" indicates that NVDA encountered an error which it wrote to its log.  It doesn't necessarily mean that you can't do whatever you were trying to do - often NVDA itself hits the error, then used a workaround, so from a user point of view, everything may still work normally.  The only difference is that in the alpha and beta builds, you get a ding, whereas in the stable release you don't and the error just writes quietly to the log.

The idea is that developers can use it to find when errors are being generated when they are working on something.

There is currently no setting to disable this, however if you are encountering a particular error that you can share how to replicate, do please report it so that we can endeavour to resolve it.

Kind regards

Quentin.

On Fri, Aug 17, 2018 at 12:17 PM, Don H <lmddh50@...> wrote:
Don't know when there is a bug in the alpha or beta versions of NVDA. When running either the Alpha or Beta versions I get a lot of error dings as I call them when browsing using Google Chrome.  For example every time i get to a edit box I get the error ding.  Sometimes just opening a web site gives me a ding.  Is there some reasoning behind such dings?







--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: Mozilla fire fox crashes with nvda 2018.3 beta 3

hurrikennyandopo ...
 

Hi guys


I downloaded the nvda 2018.3 beta 3 release made sure every thing was
cleared in the portable version then installed the new 2018.3 beta 3
release into that folder.


The same problem still is there when you go either to open say the user
guide etc through mozilla fire fox you hear a ding then fire fox crashes.


I also thought i would open it normally from the desk top and the same
thing happens it goes to open up then the browser crashes.


The alfa version does not do this and nor does the stable version of
nvda 2018.2.1 it just opens normally.


There is no add ons in nvda for the beta version and i do not think any
ting in mozilla fire fox is doing it either.


has any body got any ideas if i can not get into the browser.


I tried it with google chrome no problems there when opening a web site
only in mozilla fire fox.

It looks as though edge will open correctly as well.


The only ting i have not done is installed the beta over the stable
version not sure if it would fix it or still do the same.


I did post a debug in last night but can open the beta version of nvda
go into those browsers and show that 2 work correctly but not mozilla
fire fox.

Not sure if this would show any more to a developer.


any other ideas to try?



Gene nz

On 8/17/2018 3:48 PM, Shaun Everiss wrote:
How do you do this.

Multiprocessing is actually a good idea if your system is powerfull
enough.

Waterfox can do it if you check a box.



On 8/17/2018 3:36 PM, zahra wrote:
hi.
i never used beta versions of nvda, but i found a solution for
stopping crashing for newer versions of firefox, (firefox quantum).
the solution is disabling multiprocess in firefox.
if someone wish to do this, because of crashing or slowness of the
system, and someone has not powerful system to handel multiprocess
without problem, let me know and i explane how to disable this
horrible feature of firefox quantum!

On 8/17/18, hurrikennyandopo ... <hurrikennyandopo@hotmail.com> wrote:
Hi


If you are referring to nvda in the beta version there is no add
ons. if
it is the browser it is the same add ons that are used with the alfa
and
stable version and it or those versions do not have the problem only
the
beta. It is sorta randam but seems if you use the alfa first then turn
it off then start the beta it will happen then at times.


Gene nz



On 8/16/2018 9:12 PM, Brian's Mail list account via Groups.Io wrote:
Do you use any add ons?
Try disabling them all and then turn them on one at a time if it fixes
it.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "hurrikennyandopo ..."
<hurrikennyandopo@hotmail.com>
To: <nvda@nvda.groups.io>
Sent: Thursday, August 16, 2018 9:35 AM
Subject: Re: [nvda] Mozilla fire fox crashes with nvda 2018.3 beta 2


It seems to happen if i use the alfa snap shot first say to update
then
after i turn it off then check with the beta version it seems to
crash
but not all the time some times it will just give the message no
updates
then you can close it then other times the browser crashes.

this is only with nvda 2018.3 beta 2 not the alfa snap shot.


Gene nz



On 8/16/2018 8:24 PM, hurrikennyandopo ... wrote:
Hi guys


I do not get this problem with the alfa snapshot when i go to do the
following. help then check for update.

it will download the alfa snap shot then let me set it up.


when i go to do the same with the nvda 2018.3 beta 2 snap shot it
goes
to open the browser then crashes and then i get the following.


I thought it might of been a corrupted beta etc so totally
removed it
all settings etc then reinstalled it. Even done this with a new
fresh
copy as well.


INFO - __main__ (20:09:35.987):
Starting NVDA
INFO - core.main (20:09:36.563):
Config dir: C:\nvda beta snapshots\userConfig
INFO - config.ConfigManager._loadConfig (20:09:36.565):
Loading config: .\userConfig\nvda.ini
INFO - core.main (20:09:36.717):
NVDA version 2018.3beta2
INFO - core.main (20:09:36.717):
Using Windows version 10.0.17134 workstation
INFO - core.main (20:09:36.719):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018,
16:22:17)
[MSC v.1500 32 bit (Intel)]
INFO - core.main (20:09:36.719):
Using comtypes version 1.1.3
INFO - synthDriverHandler.setSynth (20:09:38.078):
Loaded synthDriver oneCore
INFO - core.main (20:09:38.079):
Using wx version 3.0.2.0 msw (classic)
INFO - brailleInput.initialize (20:09:38.085):
Braille input initialized
INFO - braille.initialize (20:09:38.085):
Using liblouis version 3.6.0
INFO - braille.BrailleHandler.setDisplayByName (20:09:38.088):
Loaded braille display driver noBraille, current display has 0
cells.
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (20:09:38.415):
UIAutomation: IUIAutomation5
INFO - core.main (20:09:38.915):
NVDA initialized
INFO - updateCheck.AutoUpdateChecker._started (20:09:38.993):
Performing automatic update check
ERROR - virtualBuffers.VirtualBuffer._loadBuffer (20:10:21.470):
Traceback (most recent call last):
   File "virtualBuffers\__init__.pyo", line 417, in _loadBuffer
WindowsError: [Error 1726] The remote procedure call failed
ERROR - virtualBuffers.VirtualBuffer._loadBuffer (20:11:19.418):
Traceback (most recent call last):
   File "virtualBuffers\__init__.pyo", line 417, in _loadBuffer
WindowsError: [Error 1726] The remote procedure call failed
INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo
(20:12:05.006):
Developer info for navigator object:
name: u'Tell Mozilla about this crash so they can fix it'
role: ROLE_CHECKBOX
states: STATE_CHECKED, STATE_FOCUSABLE, STATE_FOCUSED
isFocusable: True
hasFocus: True
Python object: <NVDAObjects.IAccessible.IAccessible object at
0x035D3450>
Python class mro: (<class 'NVDAObjects.IAccessible.IAccessible'>,
<class
'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>,
<class
'documentBase.TextContainerObject'>, <class
'baseObject.ScriptableObject'>, <class
'baseObject.AutoPropertyObject'>,
<type 'object'>)
description: None
location: (477, 450, 355, 16)
value: None
appModule: <'appModuleHandler' (appName u'crashreporter', process ID
9028) at address 5872650>
appModule.productName: u'Firefox'
appModule.productVersion: u'61.0.2'
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 263040
windowClassName: u'Button'
windowControlID: 1007
windowStyle: 1342242819
windowThreadID: 6616
windowText: u'Tell Mozilla about this crash so they can fix it'
displayText: u'Tell Mozilla about this crash so they can fix it'
IAccessibleObject: <POINTER(IAccessible) ptr=0x754280 at 583df30>
IAccessibleChildID: 0
IAccessible event parameters: windowHandle=263040, objectID=-4,
childID=0
IAccessible accName: u'Tell Mozilla about this crash so they can fix
it'
IAccessible accRole: ROLE_SYSTEM_CHECKBUTTON
IAccessible accState: STATE_SYSTEM_CHECKED, STATE_SYSTEM_FOCUSED,
STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1048596)
IAccessible accDescription: None
IAccessible accValue: None




n










Re: Mozilla fire fox crashes with nvda 2018.3 beta 2

 

How do you do this.

Multiprocessing is actually a good idea if your system is powerfull enough.

Waterfox can do it if you check a box.

On 8/17/2018 3:36 PM, zahra wrote:
hi.
i never used beta versions of nvda, but i found a solution for
stopping crashing for newer versions of firefox, (firefox quantum).
the solution is disabling multiprocess in firefox.
if someone wish to do this, because of crashing or slowness of the
system, and someone has not powerful system to handel multiprocess
without problem, let me know and i explane how to disable this
horrible feature of firefox quantum!

On 8/17/18, hurrikennyandopo ... <hurrikennyandopo@hotmail.com> wrote:
Hi


If you are referring to nvda in the beta version there is no add ons. if
it is the browser it is the same add ons that are used with the alfa and
stable version and it or those versions do not have the problem only the
beta. It is sorta randam but seems if you use the alfa first then turn
it off then start the beta it will happen then at times.


Gene nz



On 8/16/2018 9:12 PM, Brian's Mail list account via Groups.Io wrote:
Do you use any add ons?
Try disabling them all and then turn them on one at a time if it fixes
it.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "hurrikennyandopo ..."
<hurrikennyandopo@hotmail.com>
To: <nvda@nvda.groups.io>
Sent: Thursday, August 16, 2018 9:35 AM
Subject: Re: [nvda] Mozilla fire fox crashes with nvda 2018.3 beta 2


It seems to happen if i use the alfa snap shot first say to update then
after i turn it off then check with the beta version it seems to crash
but not all the time some times it will just give the message no updates
then you can close it then other times the browser crashes.

this is only with nvda 2018.3 beta 2 not the alfa snap shot.


Gene nz



On 8/16/2018 8:24 PM, hurrikennyandopo ... wrote:
Hi guys


I do not get this problem with the alfa snapshot when i go to do the
following. help then check for update.

it will download the alfa snap shot then let me set it up.


when i go to do the same with the nvda 2018.3 beta 2 snap shot it goes
to open the browser then crashes and then i get the following.


I thought it might of been a corrupted beta etc so totally removed it
all settings etc then reinstalled it. Even done this with a new fresh
copy as well.


INFO - __main__ (20:09:35.987):
Starting NVDA
INFO - core.main (20:09:36.563):
Config dir: C:\nvda beta snapshots\userConfig
INFO - config.ConfigManager._loadConfig (20:09:36.565):
Loading config: .\userConfig\nvda.ini
INFO - core.main (20:09:36.717):
NVDA version 2018.3beta2
INFO - core.main (20:09:36.717):
Using Windows version 10.0.17134 workstation
INFO - core.main (20:09:36.719):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17)
[MSC v.1500 32 bit (Intel)]
INFO - core.main (20:09:36.719):
Using comtypes version 1.1.3
INFO - synthDriverHandler.setSynth (20:09:38.078):
Loaded synthDriver oneCore
INFO - core.main (20:09:38.079):
Using wx version 3.0.2.0 msw (classic)
INFO - brailleInput.initialize (20:09:38.085):
Braille input initialized
INFO - braille.initialize (20:09:38.085):
Using liblouis version 3.6.0
INFO - braille.BrailleHandler.setDisplayByName (20:09:38.088):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (20:09:38.415):
UIAutomation: IUIAutomation5
INFO - core.main (20:09:38.915):
NVDA initialized
INFO - updateCheck.AutoUpdateChecker._started (20:09:38.993):
Performing automatic update check
ERROR - virtualBuffers.VirtualBuffer._loadBuffer (20:10:21.470):
Traceback (most recent call last):
  File "virtualBuffers\__init__.pyo", line 417, in _loadBuffer
WindowsError: [Error 1726] The remote procedure call failed
ERROR - virtualBuffers.VirtualBuffer._loadBuffer (20:11:19.418):
Traceback (most recent call last):
  File "virtualBuffers\__init__.pyo", line 417, in _loadBuffer
WindowsError: [Error 1726] The remote procedure call failed
INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo
(20:12:05.006):
Developer info for navigator object:
name: u'Tell Mozilla about this crash so they can fix it'
role: ROLE_CHECKBOX
states: STATE_CHECKED, STATE_FOCUSABLE, STATE_FOCUSED
isFocusable: True
hasFocus: True
Python object: <NVDAObjects.IAccessible.IAccessible object at
0x035D3450>
Python class mro: (<class 'NVDAObjects.IAccessible.IAccessible'>,
<class
'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class
'documentBase.TextContainerObject'>, <class
'baseObject.ScriptableObject'>, <class
'baseObject.AutoPropertyObject'>,
<type 'object'>)
description: None
location: (477, 450, 355, 16)
value: None
appModule: <'appModuleHandler' (appName u'crashreporter', process ID
9028) at address 5872650>
appModule.productName: u'Firefox'
appModule.productVersion: u'61.0.2'
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 263040
windowClassName: u'Button'
windowControlID: 1007
windowStyle: 1342242819
windowThreadID: 6616
windowText: u'Tell Mozilla about this crash so they can fix it'
displayText: u'Tell Mozilla about this crash so they can fix it'
IAccessibleObject: <POINTER(IAccessible) ptr=0x754280 at 583df30>
IAccessibleChildID: 0
IAccessible event parameters: windowHandle=263040, objectID=-4,
childID=0
IAccessible accName: u'Tell Mozilla about this crash so they can fix
it'
IAccessible accRole: ROLE_SYSTEM_CHECKBUTTON
IAccessible accState: STATE_SYSTEM_CHECKED, STATE_SYSTEM_FOCUSED,
STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1048596)
IAccessible accDescription: None
IAccessible accValue: None




n









Re: Mozilla fire fox crashes with nvda 2018.3 beta 2

 

hi.
i never used beta versions of nvda, but i found a solution for
stopping crashing for newer versions of firefox, (firefox quantum).
the solution is disabling multiprocess in firefox.
if someone wish to do this, because of crashing or slowness of the
system, and someone has not powerful system to handel multiprocess
without problem, let me know and i explane how to disable this
horrible feature of firefox quantum!

On 8/17/18, hurrikennyandopo ... <hurrikennyandopo@hotmail.com> wrote:
Hi


If you are referring to nvda in the beta version there is no add ons. if
it is the browser it is the same add ons that are used with the alfa and
stable version and it or those versions do not have the problem only the
beta. It is sorta randam but seems if you use the alfa first then turn
it off then start the beta it will happen then at times.


Gene nz



On 8/16/2018 9:12 PM, Brian's Mail list account via Groups.Io wrote:
Do you use any add ons?
Try disabling them all and then turn them on one at a time if it fixes
it.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "hurrikennyandopo ..."
<hurrikennyandopo@hotmail.com>
To: <nvda@nvda.groups.io>
Sent: Thursday, August 16, 2018 9:35 AM
Subject: Re: [nvda] Mozilla fire fox crashes with nvda 2018.3 beta 2


It seems to happen if i use the alfa snap shot first say to update then
after i turn it off then check with the beta version it seems to crash
but not all the time some times it will just give the message no updates
then you can close it then other times the browser crashes.

this is only with nvda 2018.3 beta 2 not the alfa snap shot.


Gene nz



On 8/16/2018 8:24 PM, hurrikennyandopo ... wrote:
Hi guys


I do not get this problem with the alfa snapshot when i go to do the
following. help then check for update.

it will download the alfa snap shot then let me set it up.


when i go to do the same with the nvda 2018.3 beta 2 snap shot it goes
to open the browser then crashes and then i get the following.


I thought it might of been a corrupted beta etc so totally removed it
all settings etc then reinstalled it. Even done this with a new fresh
copy as well.


INFO - __main__ (20:09:35.987):
Starting NVDA
INFO - core.main (20:09:36.563):
Config dir: C:\nvda beta snapshots\userConfig
INFO - config.ConfigManager._loadConfig (20:09:36.565):
Loading config: .\userConfig\nvda.ini
INFO - core.main (20:09:36.717):
NVDA version 2018.3beta2
INFO - core.main (20:09:36.717):
Using Windows version 10.0.17134 workstation
INFO - core.main (20:09:36.719):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17)
[MSC v.1500 32 bit (Intel)]
INFO - core.main (20:09:36.719):
Using comtypes version 1.1.3
INFO - synthDriverHandler.setSynth (20:09:38.078):
Loaded synthDriver oneCore
INFO - core.main (20:09:38.079):
Using wx version 3.0.2.0 msw (classic)
INFO - brailleInput.initialize (20:09:38.085):
Braille input initialized
INFO - braille.initialize (20:09:38.085):
Using liblouis version 3.6.0
INFO - braille.BrailleHandler.setDisplayByName (20:09:38.088):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (20:09:38.415):
UIAutomation: IUIAutomation5
INFO - core.main (20:09:38.915):
NVDA initialized
INFO - updateCheck.AutoUpdateChecker._started (20:09:38.993):
Performing automatic update check
ERROR - virtualBuffers.VirtualBuffer._loadBuffer (20:10:21.470):
Traceback (most recent call last):
  File "virtualBuffers\__init__.pyo", line 417, in _loadBuffer
WindowsError: [Error 1726] The remote procedure call failed
ERROR - virtualBuffers.VirtualBuffer._loadBuffer (20:11:19.418):
Traceback (most recent call last):
  File "virtualBuffers\__init__.pyo", line 417, in _loadBuffer
WindowsError: [Error 1726] The remote procedure call failed
INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo
(20:12:05.006):
Developer info for navigator object:
name: u'Tell Mozilla about this crash so they can fix it'
role: ROLE_CHECKBOX
states: STATE_CHECKED, STATE_FOCUSABLE, STATE_FOCUSED
isFocusable: True
hasFocus: True
Python object: <NVDAObjects.IAccessible.IAccessible object at
0x035D3450>
Python class mro: (<class 'NVDAObjects.IAccessible.IAccessible'>,
<class
'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class
'documentBase.TextContainerObject'>, <class
'baseObject.ScriptableObject'>, <class
'baseObject.AutoPropertyObject'>,
<type 'object'>)
description: None
location: (477, 450, 355, 16)
value: None
appModule: <'appModuleHandler' (appName u'crashreporter', process ID
9028) at address 5872650>
appModule.productName: u'Firefox'
appModule.productVersion: u'61.0.2'
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 263040
windowClassName: u'Button'
windowControlID: 1007
windowStyle: 1342242819
windowThreadID: 6616
windowText: u'Tell Mozilla about this crash so they can fix it'
displayText: u'Tell Mozilla about this crash so they can fix it'
IAccessibleObject: <POINTER(IAccessible) ptr=0x754280 at 583df30>
IAccessibleChildID: 0
IAccessible event parameters: windowHandle=263040, objectID=-4,
childID=0
IAccessible accName: u'Tell Mozilla about this crash so they can fix
it'
IAccessible accRole: ROLE_SYSTEM_CHECKBUTTON
IAccessible accState: STATE_SYSTEM_CHECKED, STATE_SYSTEM_FOCUSED,
STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1048596)
IAccessible accDescription: None
IAccessible accValue: None




n











--
By God,
were I given all the seven heavens
with all they contain
in order that
I may disobey God
by depriving an ant
from the husk of a grain of barley,
I would not do it.
imam ali


Re: nvda_snapshot_alpha or beta

Quentin Christensen
 

Hi Don,

As Joseph mentioned, the "ding" indicates that NVDA encountered an error which it wrote to its log.  It doesn't necessarily mean that you can't do whatever you were trying to do - often NVDA itself hits the error, then used a workaround, so from a user point of view, everything may still work normally.  The only difference is that in the alpha and beta builds, you get a ding, whereas in the stable release you don't and the error just writes quietly to the log.

The idea is that developers can use it to find when errors are being generated when they are working on something.

There is currently no setting to disable this, however if you are encountering a particular error that you can share how to replicate, do please report it so that we can endeavour to resolve it.

Kind regards

Quentin.

On Fri, Aug 17, 2018 at 12:17 PM, Don H <lmddh50@...> wrote:
Don't know when there is a bug in the alpha or beta versions of NVDA. When running either the Alpha or Beta versions I get a lot of error dings as I call them when browsing using Google Chrome.  For example every time i get to a edit box I get the error ding.  Sometimes just opening a web site gives me a ding.  Is there some reasoning behind such dings?







--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: nvda_snapshot_alpha or beta

 

Hi,
This "ding" sound indicates an error that NVDA has encountered. You can't really turn this off in development snapshots (alpha and beta).
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Don H
Sent: Thursday, August 16, 2018 7:17 PM
To: nvda@nvda.groups.io
Subject: [nvda] nvda_snapshot_alpha or beta

Don't know when there is a bug in the alpha or beta versions of NVDA.
When running either the Alpha or Beta versions I get a lot of error dings as I call them when browsing using Google Chrome. For example every time i get to a edit box I get the error ding. Sometimes just opening a web site gives me a ding. Is there some reasoning behind such dings?


nvda_snapshot_alpha or beta

Don H
 

Don't know when there is a bug in the alpha or beta versions of NVDA. When running either the Alpha or Beta versions I get a lot of error dings as I call them when browsing using Google Chrome. For example every time i get to a edit box I get the error ding. Sometimes just opening a web site gives me a ding. Is there some reasoning behind such dings?


Re: Am Able to Reproduce Issue with Purchasing Kindle Books

Gene
 

I almost never purchase anything from Amazon but there is a button when you purchase a Kindle version of a book that says somethin like send to my Kindle.  I don't know if this will do what people want.  But those interested can try the button and see what happens.
 
Gene

----- Original Message -----
Sent: Thursday, August 16, 2018 6:55 PM
Subject: [nvda] Am Able to Reproduce Issue with Purchasing Kindle Books

A while back, someone posted here that they were having trouble
purchasing Kindle books on the Amazon site with NVDA. I just tried to
purchase a book, and I couldn't find either the buy with one click
button or the add to cart button. After trying this with both Firefox
and Chrome with similar results, I called their disability hot line. The
representative I talked to was able to add the book to my cart, and I
was able to purchase it that way. I explained to her that others with
visual impairments who use screen reading software are also having
difficulty, and she said she would pass it along. Will just have to see
what happens.


--
Abbie Johnson Taylor, Author http://abbiescorner.wordpress.com
http://www.abbiejohnsontaylor.com abbietaylor945@... Order my new
memoir at http://www.abbiejohnsontaylor.com/memoir.htm


--
Abbie Johnson Taylor, Author
http://www.abbiejohnsontaylor.com
http://abbiescorner.wordpress.com
abbietaylor945@...



Am Able to Reproduce Issue with Purchasing Kindle Books

Abbie Taylor <abbietaylor945@...>
 

A while back, someone posted here that they were having trouble purchasing Kindle books on the Amazon site with NVDA. I just tried to purchase a book, and I couldn't find either the buy with one click button or the add to cart button. After trying this with both Firefox and Chrome with similar results, I called their disability hot line. The representative I talked to was able to add the book to my cart, and I was able to purchase it that way. I explained to her that others with visual impairments who use screen reading software are also having difficulty, and she said she would pass it along. Will just have to see what happens.


--
Abbie Johnson Taylor, Author http://abbiescorner.wordpress.com http://www.abbiejohnsontaylor.com abbietaylor945@gmail.com Order my new memoir at http://www.abbiejohnsontaylor.com/memoir.htm


--
Abbie Johnson Taylor, Author
http://www.abbiejohnsontaylor.com
http://abbiescorner.wordpress.com
abbietaylor945@gmail.com


Re: using a command prompt

Bob J
 

Brian,

I don't know the answer to your question about why some words are spelled out instead of pronounced as a word. My synthesizer spells out some words every time they are encountered, no matter the context. Perhaps it is a synthesizer thing.

I frequently incorporate batch files into some personal programming projects to accomplish tasks that would otherwise require me to write more code in the primary programming language.

I'm curious to know if you use batch files in a similar fashion or if you might be doing some things that I should consider for my own purposes.

Bob


--------------------------------------------------
From: "Brian's Mail list account via Groups.Io" <bglists=blueyonder.co.uk@groups.io>
Sent: Thursday, August 16, 2018 4:59 AM
To: <nvda@nvda.groups.io>
Subject: Re: [nvda] using a command prompt

One of the most annoying things is that some programs seem to end up having their output spelled rather than spoken as if nvda thinks there are spaces between every character. Does anyone know why this happens sometimes? I do not see it on batch file outputs but often do if running a command line program in a batch situation. Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Steve Nomer" <swnomer@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Wednesday, August 15, 2018 6:37 PM
Subject: Re: [nvda] using a command prompt


Oops! Forget my previous email, it was all my bad. I had Focus Moves
Navigator Object set to off instead of on. Sorry for the false alarm!


Steve


On 8/15/2018 12:14 PM, Steve Nomer wrote:

I believe the command window has been broken for some of us on Windows
10. An update occurred during the past several hours on my machine and
now I cannot use the command window any longer in object mode to
review the contents of the window. If reporting of dynamic changes is
on in NVDA, I do hear the activity in the window, but attempts to use
the navigation keys or change from screen view to object view are met
with complete silence. This is not good! Does anyone have any ideas
how to fix this?


Steve


On 8/15/2018 11:56 AM, Gene wrote:
Do yu mean to automatically announce it?
Try the command NVDA f5. It toggles between report dynamic content
changes on and off. You want it on.
Gene
----- Original Message -----
*From:* Don H <mailto:lmddh50@adams.net>
*Sent:* Wednesday, August 15, 2018 10:44 AM
*To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject:* [nvda] using a command prompt

Is there a way to get NVDA to read what is being shown when you run
something using a command prompt or command prompt admin?






Re: Mozilla fire fox crashes with nvda 2018.3 beta 2

hurrikennyandopo ...
 

Hi


If you are referring to nvda in the beta version there is no add ons. if
it is the browser it is the same add ons that are used with the alfa and
stable version and it or those versions do not have the problem only the
beta. It is sorta randam but seems if you use the alfa first then turn
it off then start the beta it will happen then at times.


Gene nz

On 8/16/2018 9:12 PM, Brian's Mail list account via Groups.Io wrote:
Do you use any add ons?
Try disabling them all and then turn them on one at a time if it fixes
it.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "hurrikennyandopo ..."
<hurrikennyandopo@hotmail.com>
To: <nvda@nvda.groups.io>
Sent: Thursday, August 16, 2018 9:35 AM
Subject: Re: [nvda] Mozilla fire fox crashes with nvda 2018.3 beta 2


It seems to happen if i use the alfa snap shot first say to update then
after i turn it off then check with the beta version it seems to crash
but not all the time some times it will just give the message no updates
then you can close it then other times the browser crashes.

this is only with nvda 2018.3 beta 2 not the alfa snap shot.


Gene nz



On 8/16/2018 8:24 PM, hurrikennyandopo ... wrote:
Hi guys


I do not get this problem with the alfa snapshot when i go to do the
following. help then check for update.

it will download the alfa snap shot then let me set it up.


when i go to do the same with the nvda 2018.3 beta 2 snap shot it goes
to open the browser then crashes and then i get the following.


I thought it might of been a corrupted beta etc so totally removed it
all settings etc then reinstalled it. Even done this with a new fresh
copy as well.


INFO - __main__ (20:09:35.987):
Starting NVDA
INFO - core.main (20:09:36.563):
Config dir: C:\nvda beta snapshots\userConfig
INFO - config.ConfigManager._loadConfig (20:09:36.565):
Loading config: .\userConfig\nvda.ini
INFO - core.main (20:09:36.717):
NVDA version 2018.3beta2
INFO - core.main (20:09:36.717):
Using Windows version 10.0.17134 workstation
INFO - core.main (20:09:36.719):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17)
[MSC v.1500 32 bit (Intel)]
INFO - core.main (20:09:36.719):
Using comtypes version 1.1.3
INFO - synthDriverHandler.setSynth (20:09:38.078):
Loaded synthDriver oneCore
INFO - core.main (20:09:38.079):
Using wx version 3.0.2.0 msw (classic)
INFO - brailleInput.initialize (20:09:38.085):
Braille input initialized
INFO - braille.initialize (20:09:38.085):
Using liblouis version 3.6.0
INFO - braille.BrailleHandler.setDisplayByName (20:09:38.088):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (20:09:38.415):
UIAutomation: IUIAutomation5
INFO - core.main (20:09:38.915):
NVDA initialized
INFO - updateCheck.AutoUpdateChecker._started (20:09:38.993):
Performing automatic update check
ERROR - virtualBuffers.VirtualBuffer._loadBuffer (20:10:21.470):
Traceback (most recent call last):
  File "virtualBuffers\__init__.pyo", line 417, in _loadBuffer
WindowsError: [Error 1726] The remote procedure call failed
ERROR - virtualBuffers.VirtualBuffer._loadBuffer (20:11:19.418):
Traceback (most recent call last):
  File "virtualBuffers\__init__.pyo", line 417, in _loadBuffer
WindowsError: [Error 1726] The remote procedure call failed
INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo
(20:12:05.006):
Developer info for navigator object:
name: u'Tell Mozilla about this crash so they can fix it'
role: ROLE_CHECKBOX
states: STATE_CHECKED, STATE_FOCUSABLE, STATE_FOCUSED
isFocusable: True
hasFocus: True
Python object: <NVDAObjects.IAccessible.IAccessible object at
0x035D3450>
Python class mro: (<class 'NVDAObjects.IAccessible.IAccessible'>,
<class
'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class
'documentBase.TextContainerObject'>, <class
'baseObject.ScriptableObject'>, <class
'baseObject.AutoPropertyObject'>,
<type 'object'>)
description: None
location: (477, 450, 355, 16)
value: None
appModule: <'appModuleHandler' (appName u'crashreporter', process ID
9028) at address 5872650>
appModule.productName: u'Firefox'
appModule.productVersion: u'61.0.2'
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 263040
windowClassName: u'Button'
windowControlID: 1007
windowStyle: 1342242819
windowThreadID: 6616
windowText: u'Tell Mozilla about this crash so they can fix it'
displayText: u'Tell Mozilla about this crash so they can fix it'
IAccessibleObject: <POINTER(IAccessible) ptr=0x754280 at 583df30>
IAccessibleChildID: 0
IAccessible event parameters: windowHandle=263040, objectID=-4,
childID=0
IAccessible accName: u'Tell Mozilla about this crash so they can fix
it'
IAccessible accRole: ROLE_SYSTEM_CHECKBUTTON
IAccessible accState: STATE_SYSTEM_CHECKED, STATE_SYSTEM_FOCUSED,
STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1048596)
IAccessible accDescription: None
IAccessible accValue: None




n









Re: unlabeled graphics on the web

Walker, Michael E
 

Gene, you are very correct that unlabeled graphics are skipped, no matter what navigation keys you choose. It is a serious problem. Suppose I am taking online training at work, and I have to be able to click the unlabeled graphic, and not have NVDA skip it. Suppose I know what the unlabeled graphic is, by text above or below it, and I do not have a sighted person available to click it for me. This comes up in the workplace all the time. How can we submit feedback to the developers on this? Thanks.

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Gene
Sent: Thursday, August 16, 2018 2:52 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] unlabeled graphics on the web

 

If graphics aren't labeled, then, of course, you may have a hard time determining what graphic to click.  But the question, as posed, assumes that.  Can NVDA be made to announce all graphics?  I don't think it does now.  If there is a graphic without any text, I don't think it announces it and there is no setting I know of to adjust the level of graphic announcement.  JAWS has such a setting and you were discussing that in your comparison of NVDA and JAWS.  If I am correct that there is no setting in NVDA for this, this is another way in which NVDA isn't as user definable as JAWS where it should be.  This may be a serious problem on a site where, to take an action a graphic needs to be clicked.  It might mean having to click it with the simulated mouse but to do that, it must be announced as you move through the page so you can move to it and then move the mouse to it. 

 

You may need sighted help to know which graphic to click but as far as I know, NVDA doesn't read unlabeled graphics on web pages and moving character by character doesn't read them either.  As far as I know, they are skipped as though they don't exist.

 

Gene

----- Original Message -----

Sent: Thursday, August 16, 2018 1:56 PM

Subject: Re: [nvda] unlabeled graphics on the web

 

I don't think you can do much about idiotic web site design. I think you
might be able to in Jaws, though it is often a trial and error thing as
unless you have sighted help to identify non marked controls you are
stuffed. It might be worth writing to the site admins and pointing out that
a little bit ofalt tagging would go a long way.
 Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Walker, Michael E" <michael.e.walker3@...>
To: <nvda@nvda.groups.io>
Sent: Thursday, August 16, 2018 1:27 PM
Subject: [nvda] unlabeled graphics on the web


Hi, how do I get NVDA to identify all graphics on a web page, including the
unlabeled ones, if I need to click one for example? Also, which section of
the user guide explains this in further detail? Thanks.






Re: unlabeled graphics on the web

Gene
 

If graphics aren't labeled, then, of course, you may have a hard time determining what graphic to click.  But the question, as posed, assumes that.  Can NVDA be made to announce all graphics?  I don't think it does now.  If there is a graphic without any text, I don't think it announces it and there is no setting I know of to adjust the level of graphic announcement.  JAWS has such a setting and you were discussing that in your comparison of NVDA and JAWS.  If I am correct that there is no setting in NVDA for this, this is another way in which NVDA isn't as user definable as JAWS where it should be.  This may be a serious problem on a site where, to take an action a graphic needs to be clicked.  It might mean having to click it with the simulated mouse but to do that, it must be announced as you move through the page so you can move to it and then move the mouse to it. 
 
You may need sighted help to know which graphic to click but as far as I know, NVDA doesn't read unlabeled graphics on web pages and moving character by character doesn't read them either.  As far as I know, they are skipped as though they don't exist.
 
Gene

----- Original Message -----
Sent: Thursday, August 16, 2018 1:56 PM
Subject: Re: [nvda] unlabeled graphics on the web

I don't think you can do much about idiotic web site design. I think you
might be able to in Jaws, though it is often a trial and error thing as
unless you have sighted help to identify non marked controls you are
stuffed. It might be worth writing to the site admins and pointing out that
a little bit ofalt tagging would go a long way.
 Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Walker, Michael E" <michael.e.walker3@...>
To: <nvda@nvda.groups.io>
Sent: Thursday, August 16, 2018 1:27 PM
Subject: [nvda] unlabeled graphics on the web


Hi, how do I get NVDA to identify all graphics on a web page, including the
unlabeled ones, if I need to click one for example? Also, which section of
the user guide explains this in further detail? Thanks.