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.

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

When using Windows 7 with Office 2007 installed, NVDA responds slower in dialogs such as file copy while Office supplied IME is in use #3274

Closed
nvaccessAuto opened this issue Jun 10, 2013 · 5 comments
Closed

When using Windows 7 with Office 2007 installed, NVDA responds slower in dialogs such as file copy while Office supplied IME is in use #3274

nvaccessAuto opened this issue Jun 10, 2013 · 5 comments
Labels
bug performance

Comments

@nvaccessAuto
Copy link

Reported by nvdakor on 2013-06-10 08:16
Hi,
Some Korean users reported an issue where NVDA responds slower when using Win7 and Office 2007 and while one is in a dialog such as file copy.

STR (as reported by users):

  1. Switch to IME supplied by Office 2007 (you need to install them; the ones used are Korean ones).
  2. Try some tasks such as copying files.
  3. Switch back to default IME which shipts with Windows.
  4. Do step 2. You should notice noticeable performance differences.

Notes from users:

  • This occurs if Windows 7 and Office 2007 is installed.
  • Other Office versions such as 2010 does not cause this issue when installed under Win7.
  • This affects both 32-bit and 64-bit versions of Windows 7.
  • This happens when Office supplised IME is in use, not the default one used under Windows.
  • Tested with Korean IME.

I asked users for a log to attach to this ticket.
Thanks.
@nvaccessAuto
Copy link
Author

Comment 1 by nvdakor on 2013-06-10 13:03
Hi,
One of the users who are experiencing this issue sent me the below log fragment (this was when the dialog for deleting multiple files was on focus with default IME in use):

ERROR - eventHandler.executeEvent (21:13:12):
error executing event: gainFocus on <NVDAObjects.Dynamic_DialogIAccessibleWindowNVDAObject object at 0x056317D0> with extra args of {}
Traceback (most recent call last):
 File "eventHandler.pyc", line 136, in executeEvent
 File "eventHandler.pyc", line 84, in __init__
 File "eventHandler.pyc", line 91, in next
 File "appModules\explorer.pyc", line 209, in event_gainFocus
 File "eventHandler.pyc", line 91, in next
 File "NVDAObjects\__init__.pyc", line 833, in event_gainFocus
 File "NVDAObjects\__init__.pyc", line 777, in reportFocus
 File "speech.pyc", line 317, in speakObject
 File "speech.pyc", line 235, in speakObjectProperties
 File "baseObject.pyc", line 34, in __get__
 File "baseObject.pyc", line 110, in _getPropertyViaCache
 File "NVDAObjects\behaviors.pyc", line 133, in _get_description
 File "NVDAObjects\behaviors.pyc", line 88, in getDialogText
 File "NVDAObjects\behaviors.pyc", line 88, in getDialogText
 File "NVDAObjects\behaviors.pyc", line 74, in getDialogText
 File "baseObject.pyc", line 34, in __get__
 File "baseObject.pyc", line 110, in _getPropertyViaCache
 File "NVDAObjects\IAccessible\__init__.pyc", line 991, in _get_children
 File "IAccessibleHandler.pyc", line 360, in accessibleChildren
 File "IAccessibleHandler.pyc", line 315, in normalizeIAccessible
RuntimeError: <comtypes.client.lazybind.Dispatch object at 0x05679BB0> Not an IAccessible

He also says that when JFW was running alongside NVDA, when this dialog was on focus, application error dialog came up for NVDA (didn't occur when JFW was running alone). Thanks.

@nvaccessAuto
Copy link
Author

Comment 2 by Animesh.mr (in reply to comment 1) on 2013-06-10 14:24
same hear

@nvaccessAuto
Copy link
Author

Comment 3 by jteh on 2013-06-20 01:53
It'd be great if you could try this with NVDA 2012.2 (the release before Asian input support was added) and 2012.3 (the release it was added in) and report your findings. I'm curious as to whether this is related to our Asian input support or not. Thanks.

@bhavyashah
Copy link

@josephsl Could you please request the Korean user who reported these slowdowns to test with the latest version of NVDA (now NVDA version 2017.3) as requested in @jcsteh's #3274 (comment)? CC @Brian1Gaff (user of Windows 7)

@LeonarddeR
Copy link
Collaborator

I'm closing this because the issue is getting very old and hasn't got relevant comments in a while. Furthermore, Office 2007 is getting quite old as well.

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

No branches or pull requests
3 participants
@LeonarddeR @nvaccessAuto @bhavyashah