Attachment xmplay.log added by Palacee_hun on 2010-09-09 15:42
Description:

Comment 1 by jteh on 2010-09-09 20:22
You're certain this works fine on your system with other screen readers (even Narrator) and without any screen reader running?

It'd be good to resolve odd crashes in 2010.3.
Changes:
Milestone changed from None to 2010.3

Comment 2 by briang1 on 2010-09-10 10:36
Hi, I have this dialogue open at this very moment in xp with no problems. It asks for the info giving examples etc, and I can type into the field, though I personally feel this piece of software is not accessible for more than rudamentory use, as nothing is read on the actual main display, though some object nav produces a file name and not much else really. Where ar these buttons mentioned etc?
If it is crashing, it might well be due to some other interaction. Tested on snap 814. No mouse used
Here are some dumps.
Main screen..

INFO - appModules._default.AppModule.script_navigatorObject_devInfo (11:25:43):
Developer info for navigator object:
name: None
role: ROLE_UNKNOWN
states: STATE_FOCUSABLE, STATE_FOCUSED
Python object: <NVDAObjects.IAccessible.ContentGenericClient object at 0x022FB710>
Python class mro: (<class 'NVDAObjects.IAccessible.ContentGenericClient'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)
description: None
location: (256, 192, 307, 81)
value: u'\n\x00no track\n'
appModule: <_default (appName xmplay, process ID 3196) at address 2311350>
TextInfo: <class 'displayModel.DisplayModelTextInfo'>
windowHandle: 66932
windowClassName: u'XMPLAY-INFO'
windowControlID: 0
windowStyle: -1811939328
windowThreadID: 3280
windowText: u'\x00'
IAccessibleObject: <POINTER(IAccessible) ptr=0x1b47e0 at 23060d0>
IAccessibleChildID: 0
IAccessible event parameters: windowHandle=66932, objectID=-4, childID=0
IAccessible accRole: ROLE_SYSTEM_CLIENT
IAccessible accState: STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1048580)

Open file/url screen

INFO - appModules._default.AppModule.script_navigatorObject_devInfo (11:23:20):
Developer info for navigator object:
name: u'File name:'
role: ROLE_EDITABLETEXT
states: STATE_FOCUSABLE, STATE_FOCUSED
Python object: <NVDAObjects.Dynamic_IAccessibleEditWindowNVDAObject object at 0x0239C550>
Python class mro: (<class 'NVDAObjects.Dynamic_IAccessibleEditWindowNVDAObject'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.edit.Edit'>, <class 'NVDAObjects.behaviors.EditableTextWithAutoSelectDetection'>, <class 'NVDAObjects.behaviors.EditableText'>, <class 'editableText.EditableText'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)
description: None
location: (683, 626, 229, 16)
value: u'A load of twaddle from brian'
appModule: <_default (appName xmplay, process ID 3196) at address 2311350>
TextInfo: <class 'NVDAObjects.window.edit.EditTextInfo'>
windowHandle: 66948
windowClassName: u'Edit'
windowControlID: 1152
windowStyle: 1342242944
windowThreadID: 3280
windowText: u'A load of twaddle from brian\x00'
IAccessibleObject: <POINTER(IAccessible) ptr=0x1b6a68 at 23068a0>
IAccessibleChildID: 0
IAccessible event parameters: windowHandle=66948, objectID=-4, childID=0
IAccessible accRole: ROLE_SYSTEM_TEXT
IAccessible accState: STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1048580)

output from pressing o..
IO - keyboardHandler.internal_keyDownEvent (11:28:17):
key press: o
IO - speech.speakText (11:28:17):
Speaking u'Open file(s) dialog URLs should begin with something like http:// or ftp://'
IO - speech.speakText (11:28:17):
Speaking u'File name: edit Alt+n'
IO - speech.speakText (11:28:17):
Speaking u'\x00'

end

Could be closed, but maybe there is another factor we do not know about going on here?
Brian

Comment 3 by Palacee_hun (in reply to comment 2) on 2010-09-10 12:08
Replying to briang1:

Hi, I have this dialogue open at this very moment in xp with no problems. It asks for the info giving examples etc, and I can type into the field, though I personally feel this piece of software is not accessible for more than rudamentory use, as nothing is read on the actual main display, though some object nav produces a file name and not much else really. Where ar these buttons mentioned etc?

If it is crashing, it might well be due to some other interaction. Tested on snap 814. No mouse used

Here are some dumps.

Main screen..

INFO - appModules._default.AppModule.script_navigatorObject_devInfo (11:25:43):

Developer info for navigator object:

name: None

role: ROLE_UNKNOWN

states: STATE_FOCUSABLE, STATE_FOCUSED

Python object: <NVDAObjects.IAccessible.ContentGenericClient object at 0x022FB710>

Python class mro: (<class 'NVDAObjects.IAccessible.ContentGenericClient'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)

description: None

location: (256, 192, 307, 81)

value: u'\n\x00no track\n'

appModule: <_default (appName xmplay, process ID 3196) at address 2311350>

TextInfo: <class 'displayModel.DisplayModelTextInfo'>

windowHandle: 66932

windowClassName: u'XMPLAY-INFO'

windowControlID: 0

windowStyle: -1811939328

windowThreadID: 3280

windowText: u'\x00'

IAccessibleObject: <POINTER(IAccessible) ptr=0x1b47e0 at 23060d0>

IAccessibleChildID: 0

IAccessible event parameters: windowHandle=66932, objectID=-4, childID=0

IAccessible accRole: ROLE_SYSTEM_CLIENT

IAccessible accState: STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1048580)

Open file/url screen

INFO - appModules._default.AppModule.script_navigatorObject_devInfo (11:23:20):

Developer info for navigator object:

name: u'File name:'

role: ROLE_EDITABLETEXT

states: STATE_FOCUSABLE, STATE_FOCUSED

Python object: <NVDAObjects.Dynamic_IAccessibleEditWindowNVDAObject object at 0x0239C550>

Python class mro: (<class 'NVDAObjects.Dynamic_IAccessibleEditWindowNVDAObject'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.edit.Edit'>, <class 'NVDAObjects.behaviors.EditableTextWithAutoSelectDetection'>, <class 'NVDAObjects.behaviors.EditableText'>, <class 'editableText.EditableText'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)

description: None

location: (683, 626, 229, 16)

value: u'A load of twaddle from brian'

appModule: <_default (appName xmplay, process ID 3196) at address 2311350>

TextInfo: <class 'NVDAObjects.window.edit.EditTextInfo'>

windowHandle: 66948

windowClassName: u'Edit'

windowControlID: 1152

windowStyle: 1342242944

windowThreadID: 3280

windowText: u'A load of twaddle from brian\x00'

IAccessibleObject: <POINTER(IAccessible) ptr=0x1b6a68 at 23068a0>

IAccessibleChildID: 0

IAccessible event parameters: windowHandle=66948, objectID=-4, childID=0

IAccessible accRole: ROLE_SYSTEM_TEXT

IAccessible accState: STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1048580)

output from pressing o..

IO - keyboardHandler.internal_keyDownEvent (11:28:17):

key press: o

IO - speech.speakText (11:28:17):

Speaking u'Open file(s) dialog URLs should begin with something like http:// or ftp://'

IO - speech.speakText (11:28:17):

Speaking u'File name: edit Alt+n'

IO - speech.speakText (11:28:17):

Speaking u'\x00'

end

Could be closed, but maybe there is another factor we do not know about going on here?

Brian

This surprises me much. But yes there is a factor I have not mentioned and may be relevant. I use a Hungarian language Windows XP SP3. In my attached log I manually translated the error message in the end of two lines to make it understandable for who do not speak Hungarian. This was a mistake and sorry for that.
The real, unmodified log messages when I invoke that dialog in question are as follows:

DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (13:46:33):
oleacc.AccessibleObjectFromEvent with window 2294386, objectID -4 and childID 0: -2147467259 Meghatározatlan hiba
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible.init (13:46:33):
IAccessible2::windowHandle failed: (-2147467259, 'Meghat\xe1rozatlan hiba', (None, None, None, 0, None))
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible.init (13:46:33):
Resorting to WindowFromPoint on accLocation
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible.init (13:46:33):
accLocation failed: (-2147467259, 'Meghat\xe1rozatlan hiba', (None, None, None, 0, None))

Could it be that the error message "Meghatározatlan hiba" (Hungarian for unknown error) somehow disturbs NVDA because it contains a Hungarian accented letter, and that causes the crash?

Comment 4 by Palacee_hun on 2010-09-11 10:30
To my big big surprise it turned out that the error I complained about in this ticket also occurs without any screen reader running on my system! I am fully aware that it is very important to check any suspected NVDA-application interaction bug situation without a screen reader to exclude non-NVDA specific situations, but it is only now when I have managed to get sighted assistance to do this. By the way now I can check this myself as I have an installed NVDA (snapshot 3828). Before invoking the dialog I quit it and after invoking I restart it, but XMPlay is gone!

On my Win98 system (also Hungarian) XMPlay works okay both with Jaws and Windoweyes.
I consider this app quite accessible indeed though not in the strictly "traditional" sense, but through keyboard hotkeys. In my opinion NVDA reads all needed information in this app, just the Open dialog does not work for me on my XP system due to some mysterious bug in XMPlay.

Comment 5 by briang1 on 2010-09-11 12:24
Well as it seems not to be due to nvda, then I'd say this ticket should be closed now. The only suggestion I have for this is this.
maybe it has problems with the Hungarian XP for some unknown reason, or maybe the extra security of XP if you are not running as admin will not allow non installed software to do anything really useful! However exiting with no error does not seem friendly so I'd suggest contacting the authors of xm play.

Comment 6 by jteh on 2010-09-12 22:57
Reporter indicates that this is not a problem in NVDA.
Changes:
Added labels: worksforme
State: closed