Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Improperly detected focus #1643

Closed
nvaccessAuto opened this issue Jul 3, 2011 · 2 comments
Closed

Improperly detected focus #1643

nvaccessAuto opened this issue Jul 3, 2011 · 2 comments
Labels
bug

Comments

@nvaccessAuto
Copy link

Reported by tspivey on 2011-07-03 11:15
Using NVDA 2011.2 beta 1 on Windows 7 X64 sp1,
after I use NVDA for a while I get some odd focus problems. If I open notepad, type something and hit alt f4, I hear the
text of the dialog, but tabbing says nothing. This also happens in windows update, programs and features, etc. In programs and features for example, I can navigate between the list view and the address bar, but nothing else. Focus just stays on whatever last got focussed, it seems.
I can't get it to happen when I start NVDA, and if I restart it things should get back to normal.
NVDA thinks focus is on the dialog itself, and insert f1 says:

Developer info for navigator object:
name: u'Notepad'
role: ROLE_DIALOG
states: STATE_FOCUSABLE
Python object: <NVDAObjects.Dynamic_DialogIAccessibleWindowNVDAObject object at 0x05C81D90>
Python class mro: (<class 'NVDAObjects.Dynamic_DialogIAccessibleWindowNVDAObject'>, <class 'NVDAObjects.behaviors.Dialog'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)
description: u'   Do you want to save changes to Untitled? \n'
location: (329, 297, 360, 104)
value: None
appModule: <'appModuleHandler' (appName u'notepad', process ID 4440) at address 5a6b8f0>
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 1838926
windowClassName: u'#32770'
windowControlID: 0
windowStyle: -1765277052
windowThreadID: 4456
windowText: u'Notepad'
IAccessibleObject: <POINTER(IAccessible) ptr=0x7417e70 at 5c14120>
IAccessibleChildID: 0
IAccessible event parameters: windowHandle=1838926, objectID=-4, childID=0
IAccessible accRole: ROLE_SYSTEM_DIALOG
IAccessible accState: STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1048576)
@nvaccessAuto
Copy link
Author

Comment 1 by tspivey on 2011-11-24 03:55
This seems to be Foobar 2000's fault. Moving away from that should fix it.
After adding beeps to IUIAutomationFocusChangedEventHandler_HandleFocusChangedEvent,
I noticed that I wasn't getting beeps for a while after playing/switching tracks in Foobar (due to an FB2k bug).
I'll reopen if this doesn't work.

Changes:
State: closed

@nvaccessAuto
Copy link
Author

Comment 2 by jteh on 2011-11-24 04:02
For reference, this is the foobar2000 bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nvaccessAuto