Date   
Re: Is this worry in Alpha any concern?

 

Probably not.


Leonard

Op 23-10-2019 om 12:09 schreef Brian's Mail list account via Groups.Io:


IO - inputCore.InputManager.executeGesture (11:02:17.341) - winInputHook (1792):
Input: kb(desktop):numpadPlus
IO - speech.speak (11:02:17.351) - MainThread (5304):
Speaking [<speech.commands.CallbackCommand object at 0x05CD2CD0>, LangChangeCommand ('en_GB'), ' \r\nHas anyone seen Brie?? ', <speech.commands.CallbackCommand object at 0x05CD2830>, 'ðY~» She is 7 years old white fluffy with a black tail. ']
ERROR - speech.manager.SpeechManager._handleIndex (11:02:18.175) - MainThread (5304):
Error running speech callback
Traceback (most recent call last):
 File "speech\manager.pyc", line 375, in _handleIndex
 File "speech\commands.pyc", line 260, in run
 File "sayAllHandler.pyc", line 145, in <lambda>
 File "sayAllHandler.pyc", line 174, in lineReached
 File "NVDAObjects\IAccessible\MSHTML.pyc", line 418, in makeTextInfo
 File "documentBase.pyc", line 24, in makeTextInfo
 File "NVDAObjects\IAccessible\MSHTML.pyc", line 320, in __init__
 File "comtypes\client\lazybind.pyc", line 182, in caller
 File "comtypes\automation.pyc", line 729, in _invoke
 File "comtypesMonkeyPatches.pyc", line 26, in __call__
_ctypes.COMError: (-2147024809, 'The parameter is incorrect.', (None, None, None, 0, None))
Its in one of those awful html emails some forums send out.
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



Is this worry in Alpha any concern?

Brian's Mail list account
 

IO - inputCore.InputManager.executeGesture (11:02:17.341) - winInputHook (1792):
Input: kb(desktop):numpadPlus
IO - speech.speak (11:02:17.351) - MainThread (5304):
Speaking [<speech.commands.CallbackCommand object at 0x05CD2CD0>, LangChangeCommand ('en_GB'), ' \r\nHas anyone seen Brie?? ', <speech.commands.CallbackCommand object at 0x05CD2830>, 'ðY~» She is 7 years old white fluffy with a black tail. ']
ERROR - speech.manager.SpeechManager._handleIndex (11:02:18.175) - MainThread (5304):
Error running speech callback
Traceback (most recent call last):
File "speech\manager.pyc", line 375, in _handleIndex
File "speech\commands.pyc", line 260, in run
File "sayAllHandler.pyc", line 145, in <lambda>
File "sayAllHandler.pyc", line 174, in lineReached
File "NVDAObjects\IAccessible\MSHTML.pyc", line 418, in makeTextInfo
File "documentBase.pyc", line 24, in makeTextInfo
File "NVDAObjects\IAccessible\MSHTML.pyc", line 320, in __init__
File "comtypes\client\lazybind.pyc", line 182, in caller
File "comtypes\automation.pyc", line 729, in _invoke
File "comtypesMonkeyPatches.pyc", line 26, in __call__
_ctypes.COMError: (-2147024809, 'The parameter is incorrect.', (None, None, None, 0, None))
Its in one of those awful html emails some forums send out.
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: Hmm.. Anyone had issues restarting Alpha snaps today?

Brian's Mail list account
 

OK, managed to get the crash on a normal usage in an application, in this case the webbie podcatcher which I use a lot with no issues on the stable version of nvda.
Here is what I tend to get before the logging itself gives up.

IO - inputCore.InputManager.executeGesture (10:13:30.943) - winInputHook (6124):
Input: kb(desktop):downArrow
IO - speech.speak (10:13:30.970) - MainThread (4732):
Speaking [LangChangeCommand ('en_GB'), 'Inside Health 11 of 18']
IO - inputCore.InputManager.executeGesture (10:13:33.799) - winInputHook (6124):
Input: kb(desktop):enter
IO - speech.speak (10:13:34.042) - MainThread (4732):
Speaking [LangChangeCommand ('en_GB'), 'Frame1 list']
IO - speech.speak (10:13:34.059) - MainThread (4732):
Speaking [LangChangeCommand ('en_GB'), 'Getting podcast, please wait. 1 of 1']
IO - inputCore.InputManager.executeGesture (10:13:38.086) - winInputHook (6124):
Input: kb(desktop):downArrow
IO - inputCore.InputManager.executeGesture (10:13:38.790) - winInputHook (6124):
Input: kb(desktop):upArrow
IO - inputCore.InputManager.executeGesture (10:13:41.046) - winInputHook (6124):
Input: kb(desktop):downArrow
IO - inputCore.InputManager.executeGesture (10:13:41.422) - winInputHook (6124):
Input: kb(desktop):upArrow
IO - inputCore.InputManager.executeGesture (10:13:42.263) - winInputHook (6124):
Input: kb(desktop):escape
IO - inputCore.InputManager.executeGesture (10:13:43.063) - winInputHook (6124):
Input: kb(desktop):downArrow
IO - inputCore.InputManager.executeGesture (10:13:43.463) - winInputHook (6124):
Input: kb(desktop):upArrow
IO - inputCore.InputManager.executeGesture (10:13:44.415) - winInputHook (6124):
Input: kb(desktop):downArrow
IO - inputCore.InputManager.executeGesture (10:13:44.823) - winInputHook (6124):
Input: kb(desktop):upArrow
IO - inputCore.InputManager.executeGesture (10:13:47.535) - winInputHook (6124):
Input: kb(desktop):alt+tab
DEBUGWARNING - RPC process 1660 (dwm.exe) (10:13:47.550) - Dummy-3 (4140):
Thread 4596, build\x86_64\remote\injection.cpp, inproc_winEventCallback, 66:
SetWindowsHookEx with WH_GETMESSAGE failed, GetLastError returned 5

DEBUGWARNING - RPC process 1660 (dwm.exe) (10:13:47.551) - Dummy-3 (4140):
Thread 4596, build\x86_64\remote\injection.cpp, inproc_winEventCallback, 69:
SetWindowsHookEx with WH_CALLWNDPROC failed, GetLastError returned 5

DEBUGWARNING - watchdog._watcher (10:13:47.691) - watchdog (3116):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 215, in <module>
File "core.pyc", line 532, in main
File "wx\core.pyc", line 2134, in MainLoop
File "gui\__init__.pyc", line 1003, in Notify
File "core.pyc", line 502, in run
File "queueHandler.pyc", line 83, in pumpAll
File "queueHandler.pyc", line 50, in flushQueue
File "eventHandler.pyc", line 46, in _queueEventCallback

WARNING - watchdog._watcher (10:14:02.692) - watchdog (3116):
Core frozen in stack:
File "nvda.pyw", line 215, in <module>
File "core.pyc", line 532, in main
File "wx\core.pyc", line 2134, in MainLoop
File "gui\__init__.pyc", line 1003, in Notify
File "core.pyc", line 502, in run
File "queueHandler.pyc", line 83, in pumpAll
File "queueHandler.pyc", line 50, in flushQueue
File "eventHandler.pyc", line 46, in _queueEventCallback

It is then stuffed, to give a technical term..
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-devel@groups.io>
Sent: Saturday, October 19, 2019 9:30 AM
Subject: Re: [nvda-devel] Hmm.. Anyone had issues restarting Alpha snaps today?


That is the issue it seems totally random but only affects alpha.
I blame Brexit here in the UK for it all :-)
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: "zvonimir stanecic, 9a5dsz" <zvonimirek222@...>
To: <nvda-devel@groups.io>
Sent: Friday, October 18, 2019 3:17 PM
Subject: Re: [nvda-devel] Hmm.. Anyone had issues restarting Alpha snaps today?


I cannot reproduce this myself, too.

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Luke Davis
Sent: Thursday, October 17, 2019 12:36 PM
To: NVDA Dev list on groups.io <nvda-devel@groups.io>
Subject: Re: [nvda-devel] Hmm.. Anyone had issues restarting Alpha snaps
today?

No such problems on last couple alphas on Win 10 64 bit 1903.

On Thu, 17 Oct 2019, Brian's Mail list account via Groups.Io wrote:

I did a download yesterday, and found that it locked the machine up
after the rising tones to load it. I rebooted the installed stable and
that took an age to come up, one assumes it had to force closure. This
morning another alpha update and the same thing happened again. Now of
course once it has worked once, you get no further issues so I'm
thinking it might be something to do with writing to a file which of
course cannot be logged if it cannot write to it. This is Windows 7,
but I do not know apart from one very useful change, of anything that
might appear to cause this for me, as updates seem to have been fine for
weeks till now.
Brian






Re: Names of mouse events?

derek riemer
 

Yeah, take a look in the def executeMouseMoveEvent(x,y): function of mouseHandler.py to see where the mouseMove event is fired. Your definition is going to look like

def event_mouseMove(self, x, y): for an overlay, or def event_mouseMove(self, obj, nextHandler, x, y): for any other object.


On Sat, Oct 19, 2019 at 3:29 PM Derek Riemer <driemer.riemer@...> wrote:
I think event_mouseMove might be a thing.

On Sat, Oct 19, 2019 at 6:51 AM Karl-Otto Rosenqvist <Karl-otto@...> wrote:
Hi!
I was interested in triggering my readCurrentRow() method when the user clicked in the control I’ve encapsulated in a custom class.
I was able, with the help of Joseph Lee, to implement the UIAutmationSelectionInvalidated event thus handling the mouse clicks aren’t necessary at this time anymore.

On the other hand, it would be nice if I could do some hit testing on the custom control so the user can get info about what’s below the cursor without having to click.

Where can I get info about the params that comes with eventMouseMove() or what it’s called? I’m getting better at understanding the source as my understanding of Python and NVDA gets better.


Kind regards
Karl-Otto
0701-75 98 56

Även om det är ett äpple på baksidan så får du inte tugga på min mobil!

18 okt. 2019 kl. 04:06 skrev derek riemer <driemer.riemer@...>:


Can you give us more details on how the selection model and a11y tree appear in the app you're modding? A few things that'll be useful:
mousehandler.py: The mouse handling code, which tracks the mouse.
eventHandler.py: The event tracking and pumping logic.
This is a bit gnarly, so basically, each event, besides the NVDAObject level, receives a next function, conventionally called nextHandler, that dispatches the event to the next part of the system. This way, anything in NVDA can ask to be notified about an event by declaring a method called event_<eventname> taking a self, obj, and nextHandler argument. It can drop the event chain on the floor stopping execution, by ignoring the nextHandler argument, or it can continue the chain of event propagation by calling nextHandler with no arguments. This is why there are no lists of possible events, the function to call is derived on the fly from the event name. When trying to fix mouse handling, you'll want to know about something called hit-testing, which is just fancy language that means given an x,y coordinate on screen, what element is at that coordinate. UIA and IAccessible both can do this, and the LocationHelper classes and TextInfo/obj.location properties will probably help you. I don't know how to help you further at this time, because it depends on how you have things set up.

On Wed, Oct 16, 2019 at 10:56 PM Karl-Otto Rosenqvist <Karl-otto@...> wrote:
Hi!
There’s a grid I’m trying to make accessible and if you click on it so it gains focus it speaks its selection. Because I’ve implemented gestures for the arrow keys I make it speak its selection when the user moves around in the grid with the keyboard. I’d like to make it speak if you use the mouse to change the selection so if I could trap the mouse down event I could call my method ReadGridSelection.

An alternative I could assign the SelectionInvalidated  UIA event instead. That way I could skip the keyboard gestures and let the UIA event trigger the speech. The problem is that I know how to do this in C# but not how it’s done in an app module in Python and there’s no documentation that I’ve found.


Kind regards

Karl-Otto
0701-75 98 56

Även om det är ett äpple på baksidan så får du inte tugga på min mobil!

> 16 okt. 2019 kl. 23:12 skrev James Scholes <james@...>:
>
> What exactly are you trying to do?  It doesn't seem like it should be NVDA's responsibility to handle mouse input within a separate application, create click targets, etc.  The fact that the gain focus event works, and that you can technically create handlers for space and enter to click on stuff from a keyboard perspective, are just side effects of NVDA's inner workings.
>
> Regards,
>
> James Scholes
>
>> On 16/10/2019 at 9:18 pm, Karl-Otto Rosenqvist wrote:
>> Hi!
>> I'd like to act upon mouse down/click on a control that I have an overlay class for in order to get NVDA to read its contents. I've implemented the event_gainFocus and that works the when the control gets focused regardless of if it's due to a mouse click or tabbing into it. I'd like to make it speak when it already has focus and the user clicks in a different spot on the control.
>> I haven't found any add-ons or examples on the web that I could learn from, unfortunately, and as far as I know there's no list of events somewhere?
>> Kind regards
>> Karl-Otto
>
>
>






--
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






--
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






--
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




Re: Names of mouse events?

derek riemer
 

I think event_mouseMove might be a thing.

On Sat, Oct 19, 2019 at 6:51 AM Karl-Otto Rosenqvist <Karl-otto@...> wrote:
Hi!
I was interested in triggering my readCurrentRow() method when the user clicked in the control I’ve encapsulated in a custom class.
I was able, with the help of Joseph Lee, to implement the UIAutmationSelectionInvalidated event thus handling the mouse clicks aren’t necessary at this time anymore.

On the other hand, it would be nice if I could do some hit testing on the custom control so the user can get info about what’s below the cursor without having to click.

Where can I get info about the params that comes with eventMouseMove() or what it’s called? I’m getting better at understanding the source as my understanding of Python and NVDA gets better.


Kind regards
Karl-Otto
0701-75 98 56

Även om det är ett äpple på baksidan så får du inte tugga på min mobil!

18 okt. 2019 kl. 04:06 skrev derek riemer <driemer.riemer@...>:


Can you give us more details on how the selection model and a11y tree appear in the app you're modding? A few things that'll be useful:
mousehandler.py: The mouse handling code, which tracks the mouse.
eventHandler.py: The event tracking and pumping logic.
This is a bit gnarly, so basically, each event, besides the NVDAObject level, receives a next function, conventionally called nextHandler, that dispatches the event to the next part of the system. This way, anything in NVDA can ask to be notified about an event by declaring a method called event_<eventname> taking a self, obj, and nextHandler argument. It can drop the event chain on the floor stopping execution, by ignoring the nextHandler argument, or it can continue the chain of event propagation by calling nextHandler with no arguments. This is why there are no lists of possible events, the function to call is derived on the fly from the event name. When trying to fix mouse handling, you'll want to know about something called hit-testing, which is just fancy language that means given an x,y coordinate on screen, what element is at that coordinate. UIA and IAccessible both can do this, and the LocationHelper classes and TextInfo/obj.location properties will probably help you. I don't know how to help you further at this time, because it depends on how you have things set up.

On Wed, Oct 16, 2019 at 10:56 PM Karl-Otto Rosenqvist <Karl-otto@...> wrote:
Hi!
There’s a grid I’m trying to make accessible and if you click on it so it gains focus it speaks its selection. Because I’ve implemented gestures for the arrow keys I make it speak its selection when the user moves around in the grid with the keyboard. I’d like to make it speak if you use the mouse to change the selection so if I could trap the mouse down event I could call my method ReadGridSelection.

An alternative I could assign the SelectionInvalidated  UIA event instead. That way I could skip the keyboard gestures and let the UIA event trigger the speech. The problem is that I know how to do this in C# but not how it’s done in an app module in Python and there’s no documentation that I’ve found.


Kind regards

Karl-Otto
0701-75 98 56

Även om det är ett äpple på baksidan så får du inte tugga på min mobil!

> 16 okt. 2019 kl. 23:12 skrev James Scholes <james@...>:
>
> What exactly are you trying to do?  It doesn't seem like it should be NVDA's responsibility to handle mouse input within a separate application, create click targets, etc.  The fact that the gain focus event works, and that you can technically create handlers for space and enter to click on stuff from a keyboard perspective, are just side effects of NVDA's inner workings.
>
> Regards,
>
> James Scholes
>
>> On 16/10/2019 at 9:18 pm, Karl-Otto Rosenqvist wrote:
>> Hi!
>> I'd like to act upon mouse down/click on a control that I have an overlay class for in order to get NVDA to read its contents. I've implemented the event_gainFocus and that works the when the control gets focused regardless of if it's due to a mouse click or tabbing into it. I'd like to make it speak when it already has focus and the user clicks in a different spot on the control.
>> I haven't found any add-ons or examples on the web that I could learn from, unfortunately, and as far as I know there's no list of events somewhere?
>> Kind regards
>> Karl-Otto
>
>
>






--
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






--
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




Re: Possible issue with list column numbers in alpha

Brian's Mail list account
 

Of course the now very old setting of guess the item number, for example in tabs or other lists also gives some false results and always has done as well.
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
This message sent from a Windows XP machine!

----- Original Message -----
From: "Noelia Ruiz" <nrm1977@...>
To: <nvda-devel@groups.io>
Sent: Saturday, October 19, 2019 11:58 AM
Subject: Re: [nvda-devel] Possible issue with list column numbers in alpha


OK, I wouldn't treat it as a regresion since the column numbers are reported correctly according to original object properties, as previously. The problem is that the number of commands used in table navigation results inconsistent according to the column number.
And also if we implement commands to move to specific columns. For me the better solution is to make this configurable, the same as screen layout in browse mode, but maybe in object presentation.
I will fill an issue for this.


El 19/10/2019 a las 12:40, Leonard de Ruijter escribió:
Feel free to file an issue on Github about this issue. I'm not sure whether to treat it as a regression though, probably not.


Regards,

Leonard

On 19-10-2019 11:39, Noelia Ruiz wrote:
Hello:

I'm testing with NVDA 2019.1.1 and the issue with column numbers doesn't happen, but of course hiden columns are reported by NVDA.
I understand the problem to fix this inconsistency.
At least I suppose this could be documented or configurable 🤔
Regards

El 19/10/2019 a las 11:20, Leonard de Ruijter escribió:
Hello Noelia,


Do you experience any differences in behaviour before and after this commit?

if an application is programmed correctly, it should really hide the columns (i.e. they shouldn't even be exposes by the syslistview32 control). However, this patch was written for situations where even though columns are visually hidden, they are exposed by the syslistview32 control. I hadn't thought about the numbering issue, but yes, I can see why that occurs. I have no idea what to do about it though. Walking every column to see whether it is hidden or not is very expensive.


Regards,

Leonard


Re: Names of mouse events?

Karl-Otto Rosenqvist
 

Hi!
I was interested in triggering my readCurrentRow() method when the user clicked in the control I’ve encapsulated in a custom class.
I was able, with the help of Joseph Lee, to implement the UIAutmationSelectionInvalidated event thus handling the mouse clicks aren’t necessary at this time anymore.

On the other hand, it would be nice if I could do some hit testing on the custom control so the user can get info about what’s below the cursor without having to click.

Where can I get info about the params that comes with eventMouseMove() or what it’s called? I’m getting better at understanding the source as my understanding of Python and NVDA gets better.


Kind regards
Karl-Otto
0701-75 98 56

Även om det är ett äpple på baksidan så får du inte tugga på min mobil!

18 okt. 2019 kl. 04:06 skrev derek riemer <driemer.riemer@...>:


Can you give us more details on how the selection model and a11y tree appear in the app you're modding? A few things that'll be useful:
mousehandler.py: The mouse handling code, which tracks the mouse.
eventHandler.py: The event tracking and pumping logic.
This is a bit gnarly, so basically, each event, besides the NVDAObject level, receives a next function, conventionally called nextHandler, that dispatches the event to the next part of the system. This way, anything in NVDA can ask to be notified about an event by declaring a method called event_<eventname> taking a self, obj, and nextHandler argument. It can drop the event chain on the floor stopping execution, by ignoring the nextHandler argument, or it can continue the chain of event propagation by calling nextHandler with no arguments. This is why there are no lists of possible events, the function to call is derived on the fly from the event name. When trying to fix mouse handling, you'll want to know about something called hit-testing, which is just fancy language that means given an x,y coordinate on screen, what element is at that coordinate. UIA and IAccessible both can do this, and the LocationHelper classes and TextInfo/obj.location properties will probably help you. I don't know how to help you further at this time, because it depends on how you have things set up.

On Wed, Oct 16, 2019 at 10:56 PM Karl-Otto Rosenqvist <Karl-otto@...> wrote:
Hi!
There’s a grid I’m trying to make accessible and if you click on it so it gains focus it speaks its selection. Because I’ve implemented gestures for the arrow keys I make it speak its selection when the user moves around in the grid with the keyboard. I’d like to make it speak if you use the mouse to change the selection so if I could trap the mouse down event I could call my method ReadGridSelection.

An alternative I could assign the SelectionInvalidated  UIA event instead. That way I could skip the keyboard gestures and let the UIA event trigger the speech. The problem is that I know how to do this in C# but not how it’s done in an app module in Python and there’s no documentation that I’ve found.


Kind regards

Karl-Otto
0701-75 98 56

Även om det är ett äpple på baksidan så får du inte tugga på min mobil!

> 16 okt. 2019 kl. 23:12 skrev James Scholes <james@...>:
>
> What exactly are you trying to do?  It doesn't seem like it should be NVDA's responsibility to handle mouse input within a separate application, create click targets, etc.  The fact that the gain focus event works, and that you can technically create handlers for space and enter to click on stuff from a keyboard perspective, are just side effects of NVDA's inner workings.
>
> Regards,
>
> James Scholes
>
>> On 16/10/2019 at 9:18 pm, Karl-Otto Rosenqvist wrote:
>> Hi!
>> I'd like to act upon mouse down/click on a control that I have an overlay class for in order to get NVDA to read its contents. I've implemented the event_gainFocus and that works the when the control gets focused regardless of if it's due to a mouse click or tabbing into it. I'd like to make it speak when it already has focus and the user clicks in a different spot on the control.
>> I haven't found any add-ons or examples on the web that I could learn from, unfortunately, and as far as I know there's no list of events somewhere?
>> Kind regards
>> Karl-Otto
>
>
>






--
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




Re: Names of mouse events?

Karl-Otto Rosenqvist
 

Hi!
Thanks for your 

Karl-Otto
0701-75 98 56

Även om det är ett äpple på baksidan så får du inte tugga på min mobil!

18 okt. 2019 kl. 04:06 skrev derek riemer <driemer.riemer@...>:


Can you give us more details on how the selection model and a11y tree appear in the app you're modding? A few things that'll be useful:
mousehandler.py: The mouse handling code, which tracks the mouse.
eventHandler.py: The event tracking and pumping logic.
This is a bit gnarly, so basically, each event, besides the NVDAObject level, receives a next function, conventionally called nextHandler, that dispatches the event to the next part of the system. This way, anything in NVDA can ask to be notified about an event by declaring a method called event_<eventname> taking a self, obj, and nextHandler argument. It can drop the event chain on the floor stopping execution, by ignoring the nextHandler argument, or it can continue the chain of event propagation by calling nextHandler with no arguments. This is why there are no lists of possible events, the function to call is derived on the fly from the event name. When trying to fix mouse handling, you'll want to know about something called hit-testing, which is just fancy language that means given an x,y coordinate on screen, what element is at that coordinate. UIA and IAccessible both can do this, and the LocationHelper classes and TextInfo/obj.location properties will probably help you. I don't know how to help you further at this time, because it depends on how you have things set up.

On Wed, Oct 16, 2019 at 10:56 PM Karl-Otto Rosenqvist <Karl-otto@...> wrote:
Hi!
There’s a grid I’m trying to make accessible and if you click on it so it gains focus it speaks its selection. Because I’ve implemented gestures for the arrow keys I make it speak its selection when the user moves around in the grid with the keyboard. I’d like to make it speak if you use the mouse to change the selection so if I could trap the mouse down event I could call my method ReadGridSelection.

An alternative I could assign the SelectionInvalidated  UIA event instead. That way I could skip the keyboard gestures and let the UIA event trigger the speech. The problem is that I know how to do this in C# but not how it’s done in an app module in Python and there’s no documentation that I’ve found.


Kind regards

Karl-Otto
0701-75 98 56

Även om det är ett äpple på baksidan så får du inte tugga på min mobil!

> 16 okt. 2019 kl. 23:12 skrev James Scholes <james@...>:
>
> What exactly are you trying to do?  It doesn't seem like it should be NVDA's responsibility to handle mouse input within a separate application, create click targets, etc.  The fact that the gain focus event works, and that you can technically create handlers for space and enter to click on stuff from a keyboard perspective, are just side effects of NVDA's inner workings.
>
> Regards,
>
> James Scholes
>
>> On 16/10/2019 at 9:18 pm, Karl-Otto Rosenqvist wrote:
>> Hi!
>> I'd like to act upon mouse down/click on a control that I have an overlay class for in order to get NVDA to read its contents. I've implemented the event_gainFocus and that works the when the control gets focused regardless of if it's due to a mouse click or tabbing into it. I'd like to make it speak when it already has focus and the user clicks in a different spot on the control.
>> I haven't found any add-ons or examples on the web that I could learn from, unfortunately, and as far as I know there's no list of events somewhere?
>> Kind regards
>> Karl-Otto
>
>
>






--
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




Re: Possible issue with list column numbers in alpha

Noelia Ruiz
 

OK, I wouldn't treat it as a regresion since the column numbers are reported correctly according to original object properties, as previously. The problem is that the number of commands used in table navigation results inconsistent according to the column number.
And also if we implement commands to move to specific columns. For me the better solution is to make this configurable, the same as screen layout in browse mode, but maybe in object presentation.
I will fill an issue for this.

El 19/10/2019 a las 12:40, Leonard de Ruijter escribió:
Feel free to file an issue on Github about this issue. I'm not sure whether to treat it as a regression though, probably not.
Regards,
Leonard
On 19-10-2019 11:39, Noelia Ruiz wrote:
Hello:

I'm testing with NVDA 2019.1.1 and the issue with column numbers doesn't happen, but of course hiden columns are reported by NVDA.
I understand the problem to fix this inconsistency.
At least I suppose this could be documented or configurable 🤔
Regards

El 19/10/2019 a las 11:20, Leonard de Ruijter escribió:
Hello Noelia,


Do you experience any differences in behaviour before and after this commit?

if an application is programmed correctly, it should really hide the columns (i.e. they shouldn't even be exposes by the syslistview32 control). However, this patch was written for situations where even though columns are visually hidden, they are exposed by the syslistview32 control. I hadn't thought about the numbering issue, but yes, I can see why that occurs. I have no idea what to do about it though. Walking every column to see whether it is hidden or not is very expensive.


Regards,

Leonard


Re: Possible issue with list column numbers in alpha

 

Feel free to file an issue on Github about this issue. I'm not sure whether to treat it as a regression though, probably not.


Regards,

Leonard

On 19-10-2019 11:39, Noelia Ruiz wrote:
Hello:

I'm testing with NVDA 2019.1.1 and the issue with column numbers doesn't happen, but of course hiden columns are reported by NVDA.
I understand the problem to fix this inconsistency.
At least I suppose this could be documented or configurable 🤔
Regards

El 19/10/2019 a las 11:20, Leonard de Ruijter escribió:
Hello Noelia,


Do you experience any differences in behaviour before and after this commit?

if an application is programmed correctly, it should really hide the columns (i.e. they shouldn't even be exposes by the syslistview32 control). However, this patch was written for situations where even though columns are visually hidden, they are exposed by the syslistview32 control. I hadn't thought about the numbering issue, but yes, I can see why that occurs. I have no idea what to do about it though. Walking every column to see whether it is hidden or not is very expensive.


Regards,

Leonard





Re: Possible issue with list column numbers in alpha

Noelia Ruiz
 

Hello:

I'm testing with NVDA 2019.1.1 and the issue with column numbers doesn't happen, but of course hiden columns are reported by NVDA.
I understand the problem to fix this inconsistency.
At least I suppose this could be documented or configurable 🤔
Regards

El 19/10/2019 a las 11:20, Leonard de Ruijter escribió:
Hello Noelia,
Do you experience any differences in behaviour before and after this commit?
if an application is programmed correctly, it should really hide the columns (i.e. they shouldn't even be exposes by the syslistview32 control). However, this patch was written for situations where even though columns are visually hidden, they are exposed by the syslistview32 control. I hadn't thought about the numbering issue, but yes, I can see why that occurs. I have no idea what to do about it though. Walking every column to see whether it is hidden or not is very expensive.
Regards,
Leonard

Re: Possible issue with list column numbers in alpha

 

Hello Noelia,


Do you experience any differences in behaviour before and after this commit?

if an application is programmed correctly, it should really hide the columns (i.e. they shouldn't even be exposes by the syslistview32 control). However, this patch was written for situations where even though columns are visually hidden, they are exposed by the syslistview32 control. I hadn't thought about the numbering issue, but yes, I can see why that occurs. I have no idea what to do about it though. Walking every column to see whether it is hidden or not is very expensive.


Regards,

Leonard

Possible issue with list column numbers in alpha

Noelia Ruiz
 

Hi Leonard and all:

Related to commit dbb1cf1e5e5f3f6b7895a12b037cc16b5f107f37:
Hide invisible columns in syslistview32 lists (#9873)
STR:

1. Hide some columns, for instance in eMule.
2. Navigate by columns in a list, for example servers.

Maybe expected: Report the column number according to the columns shown on the screen, not to the list item number of columns according to its object properties, so that the number reported agrees with the navigable columns.

Result: the reported number is based on the object properties.
Also, why should the moveToColumnNumber method be marked asprivate? This is just a question for which I'm curious. I use this method in eMule add-on and I am just working on it, so I have seen the mentioned issue.

Cheers

Re: Hmm.. Anyone had issues restarting Alpha snaps today?

Brian's Mail list account
 

That is the issue it seems totally random but only affects alpha.
I blame Brexit here in the UK for it all :-)
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: "zvonimir stanecic, 9a5dsz" <zvonimirek222@...>
To: <nvda-devel@groups.io>
Sent: Friday, October 18, 2019 3:17 PM
Subject: Re: [nvda-devel] Hmm.. Anyone had issues restarting Alpha snaps today?


I cannot reproduce this myself, too.

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Luke Davis
Sent: Thursday, October 17, 2019 12:36 PM
To: NVDA Dev list on groups.io <nvda-devel@groups.io>
Subject: Re: [nvda-devel] Hmm.. Anyone had issues restarting Alpha snaps
today?

No such problems on last couple alphas on Win 10 64 bit 1903.

On Thu, 17 Oct 2019, Brian's Mail list account via Groups.Io wrote:

I did a download yesterday, and found that it locked the machine up
after the rising tones to load it. I rebooted the installed stable and
that took an age to come up, one assumes it had to force closure. This
morning another alpha update and the same thing happened again. Now of
course once it has worked once, you get no further issues so I'm
thinking it might be something to do with writing to a file which of
course cannot be logged if it cannot write to it. This is Windows 7,
but I do not know apart from one very useful change, of anything that
might appear to cause this for me, as updates seem to have been fine for
weeks till now.
Brian




Re: Hmm.. Anyone had issues restarting Alpha snaps today?

Brian's Mail list account
 

Yes what I was referring to was to get it to reboot when its in the mood to crash, as by definition you are typing blind and probably not typing to anything!

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: "Cyrille via Groups.Io" <cyrille.bougot2=laposte.net@groups.io>
To: <nvda-devel@groups.io>
Sent: Friday, October 18, 2019 8:51 AM
Subject: Re : Re: [nvda-devel] Hmm.. Anyone had issues restarting Alpha snaps today?


To restart NVDA with add-ons disabled, you can press Windows+R and type the following:
nvda -r --disable-addons
Then press Enter.

Once you have restarted without add-ons, you may disable the suspected add-on and restart normally.

Cheers,

Cyrille


----- Mail d'origine -----De: Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io>&Agrave;: nvda-devel@...&eacute;: Fri, 18 Oct 2019 09:37:39 +0200 (CEST)Objet: Re: [nvda-devel] Hmm.. Anyone had issues restarting Alpha snaps today?

I'm suspicious that it might be something to do with the new dev version of the sounds add on. I'll need to deactivate it and wait for some more updates to the alpha to tell. It cannot be proved simply by restarting with add ons off as by definition, when its locked you cannot go in and turn stuff off!

Brian

bglists@... 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: "Luke Davis" <luke@...>To: "NVDA Dev list on groups.io" <nvda-devel@groups.io>Sent: Thursday, October 17, 2019 10:36 AMSubject: Re: [nvda-devel] Hmm.. Anyone had issues restarting Alpha snaps today?

No such problems on last couple alphas on Win 10 64 bit 1903.>> On Thu, 17 Oct 2019, Brian's Mail list account via Groups.Io wrote:>>> I did a download yesterday, and found that it locked the machine up after >> the rising tones to load it. I rebooted the installed stable and that >> took an age to come up, one assumes it had to force closure. This morning >> another alpha update and the same thing happened again. Now of course >> once it has worked once, you get no further issues so I'm thinking it >> might be something to do with writing to a file which of course cannot be
>> logged if it cannot write to it. This is Windows 7, but I do not know apart from one very useful change, of anything that might appear to
cause >> this for me, as updates seem to have been fine for weeks till now.>> Brian>> >




Re: Hmm.. Anyone had issues restarting Alpha snaps today?

zvonimir stanečić, 9a5dsz
 

I cannot reproduce this myself, too.

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Luke Davis
Sent: Thursday, October 17, 2019 12:36 PM
To: NVDA Dev list on groups.io <nvda-devel@groups.io>
Subject: Re: [nvda-devel] Hmm.. Anyone had issues restarting Alpha snaps
today?

No such problems on last couple alphas on Win 10 64 bit 1903.

On Thu, 17 Oct 2019, Brian's Mail list account via Groups.Io wrote:

I did a download yesterday, and found that it locked the machine up
after the rising tones to load it. I rebooted the installed stable and
that took an age to come up, one assumes it had to force closure. This
morning another alpha update and the same thing happened again. Now of
course once it has worked once, you get no further issues so I'm
thinking it might be something to do with writing to a file which of
course cannot be logged if it cannot write to it. This is Windows 7,
but I do not know apart from one very useful change, of anything that
might appear to cause this for me, as updates seem to have been fine for
weeks till now.
Brian

Re : Re: [nvda-devel] Hmm.. Anyone had issues restarting Alpha snaps today?

Cyrille
 

To restart NVDA with add-ons disabled, you can press Windows+R and type the following:
nvda -r --disable-addons
Then press Enter.
Once you have restarted without add-ons, you may disable the suspected add-on and restart normally.
Cheers,
Cyrille
----- Mail d'origine -----
De: Brian's Mail list account via Groups.Io <bglists@...>
À: nvda-devel@groups.io
Envoyé: Fri, 18 Oct 2019 09:37:39 +0200 (CEST)
Objet: Re: [nvda-devel] Hmm.. Anyone had issues restarting Alpha snaps today?
I'm suspicious that it might be something to do with the new dev version of
the sounds add on. I'll need to deactivate it and wait for some more updates
to the alpha to tell. It cannot be proved simply by restarting with add ons
off as by definition, when its locked you cannot go in and turn stuff off!
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: "Luke Davis" <luke@...>
To: "NVDA Dev list on groups.io" <nvda-devel@groups.io>
Sent: Thursday, October 17, 2019 10:36 AM
Subject: Re: [nvda-devel] Hmm.. Anyone had issues restarting Alpha snaps
today?

> No such problems on last couple alphas on Win 10 64 bit 1903.
>
> On Thu, 17 Oct 2019, Brian's Mail list account via Groups.Io wrote:
>
>> I did a download yesterday, and found that it locked the machine up after
>> the rising tones to load it. I rebooted the installed stable and that
>> took an age to come up, one assumes it had to force closure. This morning
>> another alpha update and the same thing happened again. Now of course
>> once it has worked once, you get no further issues so I'm thinking it
>> might be something to do with writing to a file which of course cannot be
>> logged if it cannot write to it. This is Windows 7, but I do not know
>> apart from one very useful change, of anything that might appear to cause
>> this for me, as updates seem to have been fine for weeks till now.
>> Brian
>
>
>

Re: Hmm.. Anyone had issues restarting Alpha snaps today?

Brian's Mail list account
 

I'm suspicious that it might be something to do with the new dev version of the sounds add on. I'll need to deactivate it and wait for some more updates to the alpha to tell. It cannot be proved simply by restarting with add ons off as by definition, when its locked you cannot go in and turn stuff off!

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: "Luke Davis" <luke@...>
To: "NVDA Dev list on groups.io" <nvda-devel@groups.io>
Sent: Thursday, October 17, 2019 10:36 AM
Subject: Re: [nvda-devel] Hmm.. Anyone had issues restarting Alpha snaps today?


No such problems on last couple alphas on Win 10 64 bit 1903.

On Thu, 17 Oct 2019, Brian's Mail list account via Groups.Io wrote:

I did a download yesterday, and found that it locked the machine up after the rising tones to load it. I rebooted the installed stable and that took an age to come up, one assumes it had to force closure. This morning another alpha update and the same thing happened again. Now of course once it has worked once, you get no further issues so I'm thinking it might be something to do with writing to a file which of course cannot be logged if it cannot write to it. This is Windows 7, but I do not know apart from one very useful change, of anything that might appear to cause this for me, as updates seem to have been fine for weeks till now.
Brian

Re: Names of mouse events?

derek riemer
 

Can you give us more details on how the selection model and a11y tree appear in the app you're modding? A few things that'll be useful:
mousehandler.py: The mouse handling code, which tracks the mouse.
eventHandler.py: The event tracking and pumping logic.
This is a bit gnarly, so basically, each event, besides the NVDAObject level, receives a next function, conventionally called nextHandler, that dispatches the event to the next part of the system. This way, anything in NVDA can ask to be notified about an event by declaring a method called event_<eventname> taking a self, obj, and nextHandler argument. It can drop the event chain on the floor stopping execution, by ignoring the nextHandler argument, or it can continue the chain of event propagation by calling nextHandler with no arguments. This is why there are no lists of possible events, the function to call is derived on the fly from the event name. When trying to fix mouse handling, you'll want to know about something called hit-testing, which is just fancy language that means given an x,y coordinate on screen, what element is at that coordinate. UIA and IAccessible both can do this, and the LocationHelper classes and TextInfo/obj.location properties will probably help you. I don't know how to help you further at this time, because it depends on how you have things set up.


On Wed, Oct 16, 2019 at 10:56 PM Karl-Otto Rosenqvist <Karl-otto@...> wrote:
Hi!
There’s a grid I’m trying to make accessible and if you click on it so it gains focus it speaks its selection. Because I’ve implemented gestures for the arrow keys I make it speak its selection when the user moves around in the grid with the keyboard. I’d like to make it speak if you use the mouse to change the selection so if I could trap the mouse down event I could call my method ReadGridSelection.

An alternative I could assign the SelectionInvalidated  UIA event instead. That way I could skip the keyboard gestures and let the UIA event trigger the speech. The problem is that I know how to do this in C# but not how it’s done in an app module in Python and there’s no documentation that I’ve found.


Kind regards

Karl-Otto
0701-75 98 56

Även om det är ett äpple på baksidan så får du inte tugga på min mobil!

> 16 okt. 2019 kl. 23:12 skrev James Scholes <james@...>:
>
> What exactly are you trying to do?  It doesn't seem like it should be NVDA's responsibility to handle mouse input within a separate application, create click targets, etc.  The fact that the gain focus event works, and that you can technically create handlers for space and enter to click on stuff from a keyboard perspective, are just side effects of NVDA's inner workings.
>
> Regards,
>
> James Scholes
>
>> On 16/10/2019 at 9:18 pm, Karl-Otto Rosenqvist wrote:
>> Hi!
>> I'd like to act upon mouse down/click on a control that I have an overlay class for in order to get NVDA to read its contents. I've implemented the event_gainFocus and that works the when the control gets focused regardless of if it's due to a mouse click or tabbing into it. I'd like to make it speak when it already has focus and the user clicks in a different spot on the control.
>> I haven't found any add-ons or examples on the web that I could learn from, unfortunately, and as far as I know there's no list of events somewhere?
>> Kind regards
>> Karl-Otto
>
>
>






--
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




Re: UIA handler code

derek riemer
 

Are you trying to ask a specific question?

On Thu, Oct 17, 2019 at 4:31 AM francisco del roio <francipvb@...> wrote:
El 17/10/2019 a las 07:26, francisco del roio escribió:
> source/_UIAHandler.py, line 345
>>              import NVDAObjects.UIA
>>              if (
>>                      isinstance(focus, NVDAObjects.UIA.UIA)
>>                      and self.clientObject.compareElements(focus.UIAElement, sender)
>>              ):
>>                      pass

Ah, I stopped here, but looking forward it makes no sense anyway...
--
Cuando tus fuerzas terminan, las de mi Dios comienzan.





--
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