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.

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

Input composition fails in PuTTY #3432

Closed
nvaccessAuto opened this Issue Aug 10, 2013 · 6 comments

Comments

Projects
None yet
2 participants
@nvaccessAuto

nvaccessAuto commented Aug 10, 2013

Reported by advck1123 on 2013-08-10 14:13
Hi.Using NVDA version next-9468,d740972
I'am input Korean latter in pertty
I'am attached my log.
ERROR - queueHandler.flushQueue (22:55:16):
Error in func handleInputCompositionStart from eventQueue
Traceback (most recent call last):
File "queueHandler.pyc", line 47, in flushQueue
File "NVDAHelper.pyc", line 157, in handleInputCompositionStart
File "NVDAObjects__init__.pyc", line 79, in call
File "appModules\putty.pyc", line 18, in chooseNVDAObjectOverlayClasses
AttributeError: 'InputComposition' object has no attribute 'IAccessibleRole'
ERROR - queueHandler.flushQueue (22:55:16):
Error in func handleInputCompositionStart from eventQueue
Traceback (most recent call last):
File "queueHandler.pyc", line 47, in flushQueue
File "NVDAHelper.pyc", line 157, in handleInputCompositionStart
File "NVDAObjects__init__.pyc", line 79, in call
File "appModules\putty.pyc", line 18, in chooseNVDAObjectOverlayClasses
AttributeError: 'InputComposition' object has no attribute 'IAccessibleRole'

@nvaccessAuto

This comment has been minimized.

nvaccessAuto commented Aug 10, 2013

Comment 1 by jteh on 2013-08-10 14:28
Technical: The putty app module's chooseNVDAObjectOverlayClasses shouldn't assume that the object is an IAccessible NVDAObject.
Changes:
Changed title from "NVDA Korean input error in PERTTY" to "Input composition fails in PuTTY"
Milestone changed from None to 2013.2

@nvaccessAuto

This comment has been minimized.

nvaccessAuto commented Aug 10, 2013

Comment 2 by advck1123 (in reply to comment 1) on 2013-08-10 14:40
jteh:
Thanks!

@nvaccessAuto

This comment has been minimized.

nvaccessAuto commented Aug 29, 2013

Comment 3 by jteh on 2013-08-29 05:46
Changes:
Milestone changed from 2013.2 to next

@nvaccessAuto

This comment has been minimized.

nvaccessAuto commented Nov 27, 2013

Comment 5 by jteh on 2013-11-27 07:16
Err, Mick, did you rebase next or something when you committed this? t3432 fixes this in 33e2e56, but next does it in ef19ae9.

Anyway, incubated in ef19ae9.
Changes:
Added labels: incubating

@nvaccessAuto

This comment has been minimized.

nvaccessAuto commented Dec 12, 2013

Comment 6 by Michael Curran <mick@... on 2013-12-12 04:19
In [bb84e8c]:

Merge branch 't3432'. Fixes #3432

Changes:
Removed labels: incubating
State: closed

@nvaccessAuto

This comment has been minimized.

nvaccessAuto commented Dec 12, 2013

Comment 7 by mdcurran on 2013-12-12 04:20
Changes:
Milestone changed from next to 2014.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment