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

canot edit number formatting in Word 2010 numbering configuration dialog #4677

Open
nvaccessAuto opened this issue Dec 9, 2014 · 4 comments
Open

canot edit number formatting in Word 2010 numbering configuration dialog #4677

nvaccessAuto opened this issue Dec 9, 2014 · 4 comments
Assignees
@michaelDCurran
Labels
app/microsoft-office bug/regression bug p4 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority

Comments

@nvaccessAuto
Copy link

Reported by peter on 2014-12-09 07:51
Hi devs,
It is not possible to edit number format in numbering configuration dialog. I checked older versions of nvda, it worked in 2014.2, the ms word updates in 2014.3 broke something and it does not work also in curent master branch. Steps to reproduce:

  1. open word 2010
  2. enable styles dialog (home>styles...
  3. you are now probably in styles window. If not, then press f6 to go there
  4. Press "new style" button
  5. type style name, tab to "style type" and choose "list"
  6. tab to format menu button, expand it and choose "numbering"
  7. tab to "enter formatting for number" and check that this field is not editable. You can see there a part of document. This field contains symbolic representation of numbering format and it is possible to edit it with nvda 2014.2 and older.
    regards
    Peter
@nvaccessAuto
Copy link
Author

Comment 2 by leonarddr on 2014-12-09 16:50
Changes:
Changed title from "canot edit number formatting in numbering configuration dialog" to "canot edit number formatting in Word 2010 numbering configuration dialog"

@nvaccessAuto nvaccessAuto added the p4 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority label Jul 5, 2016
@Adriani90
Copy link
Collaborator

@peter are you still able to reproduce this issue?

@Adriani90
Copy link
Collaborator

Testing with NVDA 2019.1.1 and MS Word 2010, when tabbing to the edit field for formating the numbering symbols, I get following error and navigation through the field is not possible at all:

IO - inputCore.InputManager.executeGesture (19:59:15.089):
Input: kb(laptop):tab
ERROR - baseObject.ScriptableObject.bindGestures (19:59:15.147):
Error binding script caret_changeSelection in <NVDAObjects.Dynamic_WordDocument_WwNIAccessibleWindowNVDAObject object at 0x055F2250>
ERROR - baseObject.ScriptableObject.bindGestures (19:59:15.191):
Error binding script caret_changeSelection in <NVDAObjects.Dynamic_WordDocument_WwNIAccessibleWindowNVDAObject object at 0x055F2250>
ERROR - baseObject.ScriptableObject.bindGestures (19:59:15.233):
Error binding script caret_moveByLine in <NVDAObjects.Dynamic_WordDocument_WwNIAccessibleWindowNVDAObject object at 0x055F2250>
ERROR - baseObject.ScriptableObject.bindGestures (19:59:15.270):
Error binding script caret_moveByLine in <NVDAObjects.Dynamic_WordDocument_WwNIAccessibleWindowNVDAObject object at 0x055F2250>
ERROR - baseObject.ScriptableObject.bindGestures (19:59:15.309):
Error binding script caret_changeSelection in <NVDAObjects.Dynamic_WordDocument_WwNIAccessibleWindowNVDAObject object at 0x055F2250>
ERROR - baseObject.ScriptableObject.bindGestures (19:59:15.345):
Error binding script caret_changeSelection in <NVDAObjects.Dynamic_WordDocument_WwNIAccessibleWindowNVDAObject object at 0x055F2250>
IO - inputCore.logTimeSinceInput (19:59:15.997):
0.908 sec since input
IO - speech.speak (19:59:15.999):
Speaking [u'Modify Multilevel list  Dialogfeld  Number format\nPosition']
IO - inputCore.logTimeSinceInput (19:59:16.006):
0.916 sec since input
IO - speech.speak (19:59:16.006):
Speaking [u'Enter formatting for number:  Eingabefeld  *)']
IO - inputCore.InputManager.executeGesture (19:59:19.019):
Input: kb(laptop):leftArrow
IO - inputCore.InputManager.executeGesture (19:59:19.640):
Input: kb(laptop):rightArrow
IO - inputCore.InputManager.executeGesture (19:59:19.953):
Input: kb(laptop):downArrow
IO - inputCore.InputManager.executeGesture (19:59:20.391):
Input: kb(laptop):upArrow

@lukaszgo1 could the approach you used to solve the find dialog in Excel also work for this one?
cc: @LeonarddeR I guess this is another display model implementation case. Right?

@lukaszgo1
Copy link
Contributor

It isn't related to display mode at all. The error from your log looks very similar to #9250

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

@michaelDCurran michaelDCurran

Labels
app/microsoft-office bug/regression bug p4 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@lukaszgo1 @michaelDCurran @nvaccessAuto @Adriani90