-
-
Notifications
You must be signed in to change notification settings - Fork 632
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
Vip mud script #1728
Comments
Comment 1 by jteh on 2011-08-21 18:41 Here is some code review. Please address these comments and update the module. First, the header comments need to be changed to conform with the rest of the NVDA code. Something like this:
Unused imports. Please remove.
Is there any reason you're using _get_states here instead of the property? If not, please change this to obj.states.
...
This can be done far more efficiently:
Note that you don't even need the if check, as it's not an error to delete a slice which doesn't exist; the slice is just considered empty. Thanks again. |
Comment 2 by dwillemv (in reply to comment 1) on 2011-08-22 09:29 |
Comment 3 by dwillemv (in reply to comment 1) on 2011-08-28 13:15 |
Comment 4 by jteh on 2011-08-29 06:37 Just a few final things that I missed in my last review (sorry!):
This comment is probably better done as the module docstring. Put something like this just above or below the imports:
Because Python has exception handling and it's going to check the length anyway, it's probably more efficient to catch exceptions than check the length, like this:
I notice you've commented out this line:
Was this intentional? If so, the line should just be removed. |
Attachment vipmud.py added by dwillemv on 2011-08-29 12:26 |
Comment 5 by dwillemv on 2011-08-29 12:29 |
Comment 6 by Bernd on 2012-06-11 22:27 |
Comment 7 by jteh on 2012-06-12 00:50 |
Comment 8 by dwillemv (in reply to comment 7) on 2012-06-12 05:12 |
Comment 9 by jteh on 2012-06-12 06:32 |
Reported by dwillemv on 2011-08-19 08:33
As vip mud (a mud client for the blind) is unkind enough to not support the NVDA API, we created a script to allow for speaking of incoming text for inclusion in NVDA. The script appears stable, but it may require further testing.
The text was updated successfully, but these errors were encountered: