Hello,
Firstly, I'm posting this here, so we can see if other screen reader users (specially with NVDA) have the issue mentioned below. I've wrote to the developers personally, but it seams that they can't reproduce it for one reason or another.
I've updated my copy of Daum PotPlayer to the latest version (1.6.51480). And as a visually impaired screen reader user, I was pleasantly surprised by the new accessibility features and improvements. Thanks very much for your efforts! I really appreciate it!
But I've found a bug with this new version. Constant crashes of the application, even on start, with the NVDA screen reader running. As soon as I launch Daum PotPlayer, with the NVDA screen reader running, Daum PotPlayer will crash with the standard “Daum PotPlayer has stopped working…” error message from Windows and the only option to close the program. This happens only with NVDA on a Windows 8.1 64-bit machine.
After some deeper experimenting, I've managed to reproduce it not only with NVDA, but with JAWS and Narrator as well. Reproducing it with NVDA is easiest, specially on a 64-bit machine (I don't know why, but it is harder on a 32-bit machine). To reproduce it with JAWS and Narrator, the user has to do object parsing/navigation with the corresponding screen reader in the main window of PotPlayer. Object parsing/navigation with Narrator is done via the Caps Lock Key and the arrow keys. Left arrow for previous object on the same object hierarchy level, right arrow for the next object on the same hierarchy level,, up arrow for the parent object in the hierarchy level and down arrow for the children object in the hierarchy level. You press and hold the Caps Lock key and do the navigation/parsing via the arrow keys. But it is a little tricky to reproduce it that way. I think the problem is the object for witch all 3 screen readers report something like "TITLE". I think that is some sort of static read-only text field. Here's what NVDA's log reports about it:
======
Developer info for navigator object:
name: u'TITLE'
role: ROLE_STATICTEXT
states: STATE_READONLY
isFocusable: False
hasFocus: False
Python object: <NVDAObjects.IAccessible.IAccessible object at 0x055ECE90>
Python class mro: (<class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)
description: u''
location: (0, 0, 10, 10)
value: u''
appModule: <'appModuleHandler' (appName u'potplayermini64', process ID 5944) at address 5515410>
appModule.productName: u'PotPlayer'
appModule.productVersion: u'0, 0, 0, 0'
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 30802954
windowClassName: u'PotPlayer64'
windowControlID: 11929545
windowStyle: -1764818944
windowThreadID: 6832
windowText: u'Daum PotPlayer'
displayText: u''
IAccessibleObject: <POINTER(IAccessible) ptr=0xf270a08 at 54d7ee0>
IAccessibleChildID: 0
IAccessible event parameters: windowHandle=30802954, objectID=-4, childID=0
IAccessible accName: u'TITLE'
IAccessible accRole: ROLE_SYSTEM_STATICTEXT
IAccessible accState: STATE_SYSTEM_READONLY, STATE_SYSTEM_VALID (64)
IAccessible accDescription: u''
IAccessible accValue: u''
======
Reproducing it with an installed copy of NVDA is easiest, because then PotPlayer will most likely crash a few seconds after start while on focus. But as I said, it can be reproduced with JAWS and Narrator as well, though it it is a little bit harder to do it.
Thanks much in advance!