Comment 1 by jteh on 2013-04-21 01:10
What type of edit control does this editor use? It sounds like it's resorting to display model, which has never supported selection tracking. However, this doesn't make sense if you know someone else who is using it just fine. NVDA+f1 output from both you and this other NVDA user would be helpful.

For what it's worth, I use Notepad++, but I don't have line wrapping enabled (and don't need it).

Comment 2 by briang1 on 2013-04-21 09:26

I've been playing with this editor as well in XP and I cannot get it to say selected either.

Developer info for navigator object:
name: None
role: ROLE_EDITABLETEXT
states: STATE_FOCUSABLE, STATE_FOCUSED
isFocusable: True
hasFocus: True
Python object: <NVDAObjects.Dynamic_IAccessibleDisplayModelEditableTextWindowNVDAObject object at 0x03F64BD0>
Python class mro: (<class 'NVDAObjects.Dynamic_IAccessibleDisplayModelEditableTextWindowNVDAObject'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.DisplayModelEditableText'>, <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: (66, 117, 733, 433)
value: u'This is a test only\r\nnothing\r\n'
appModule: <'appModuleHandler' (appName u'tednpad', process ID 2304) at address 1d61890>
TextInfo: <class 'displayModel.EditableTextDisplayModelTextInfo'>
windowHandle: 1442484
windowClassName: u'TedEditW'
windowControlID: 1020
windowStyle: 1377828864
windowThreadID: 1464
windowText: u'This is a test only\r\nnothing\r\n'
displayText: u'\x00This is a test only \n\x00nothing\n\n'
IAccessibleObject: <POINTER(IAccessible) ptr=0x1e5ee0 at 1e08850>
IAccessibleChildID: 0
IAccessible event parameters: windowHandle=1442484, objectID=-4, childID=0
IAccessible accName: None
IAccessible accRole: ROLE_SYSTEM_TEXT
IAccessible accState: STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1048580)
IAccessible accDescription: None
IAccessible accValue: u'This is a test only\r\nnothing\r\n'

When you do a select all and then use nvda/F you get no formatting information.
Otherwise you get
IO - speech.speak (10:18:14):
Speaking ('en_UK'), u'Courier New 7pt black on white'

When you are selecting text there is no speech as if it cannot read the text under the cursor.

Comment 3 by jteh on 2013-04-21 10:05
This is definitely using display hooks, so reporting of selection won't work. The question is why it is different for the one user for whom it works. The only thing i can think is that it uses UIA, but the reporter is using Windows 7, so UIA should work fine.

Comment 4 by briang1 on 2013-04-21 10:55
Might be worth both looking at the version number of it. Mine is dated 2011, which I understood to be the latest version of the portable archive, but I see an installer on their site as well as a list of various files and versions which I nver investigated.

Comment 5 by camlorn on 2013-04-21 17:25
I'll try to get it from him, but I'm on the latest version (the 2011 one). Here's my nvda+f1 output. I'm going to assume that it probably is just display model, from the looks of things. I'm not going to advocate writing a module for this specific editor or anything, and probably wouldn't have bothered opening this ticket except that a whole bunch of editors do this. I'll try to get his NVDA+F1 output, if I can; I don't know him well (someone from Alter Aeon, basically, on a public channel).
Time, perhaps, to open a ticket about getting display model to support selection. it'd probably improve a lot of things.

Developer info for navigator object:
name: None
role: ROLE_EDITABLETEXT
states: STATE_FOCUSABLE, STATE_FOCUSED
isFocusable: True
hasFocus: True
Python object: <NVDAObjects.Dynamic_IAccessibleDisplayModelEditableTextWindowNVDAObject object at 0x065DB590>
Python class mro: (<class 'NVDAObjects.Dynamic_IAccessibleDisplayModelEditableTextWindowNVDAObject'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.DisplayModelEditableText'>, <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: (102, 142, 931, 644)
value: u''
appModule: <'appModuleHandler' (appName u'tednpad', process ID 3144) at address 65dbf90>
TextInfo: <class 'displayModel.EditableTextDisplayModelTextInfo'>
windowHandle: 459638
windowClassName: u'TedEditW'
windowControlID: 1020
windowStyle: 1377828864
windowThreadID: 5768
windowText: u''
displayText: ''
IAccessibleObject: <POINTER(IAccessible) ptr=0x5d0808 at 63e9710>
IAccessibleChildID: 0
IAccessible event parameters: windowHandle=459638, objectID=-4, childID=0
IAccessible accName: None
IAccessible accRole: ROLE_SYSTEM_TEXT
IAccessible accState: STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1048580)
IAccessible accDescription: None
IAccessible accValue: u''

Comment 6 by jteh (in reply to comment 5) on 2013-04-21 23:13
Replying to camlorn:

I'm not going to advocate writing a module for this specific editor or anything

We couldn't anyway unless the editor supports its own API to retrieve information related to editable text.

and probably wouldn't have bothered opening this ticket except that a whole bunch of editors do this.

That's because they don't expose editable text information using IAccessible2 or UIA.

Time, perhaps, to open a ticket about getting display model to support selection.

That's #770. However, using display hooks for anything, particularly editable text fields, is always potentially inaccurate and unreliable. This applies for other screen readers as well. API based access is a far better way to go.

@jcsteh Could you please clarify if your #3178 (comment) implies that this ticket should be closed as a cantfix and partial duplicate?

#770 is now fixed and should have in turn fixed this. However, given the inherent inconsistency/unreliability of display hooking, we can't be certain as to whether it actually fixes the problem for this particular editor without specific testing.

@Camlorn, is TED Notepad something you still care about or should we close this?

This is a friendly reminder for @camlorn to please respond to @jcsteh's #3178 (comment).

@briang1, @brian1gaf, @camlorn is this issue still reproducible with last version of NVDA and last editor version?

Closing, as we seem to have lost contact with the original author of this issue.