Date   
Strange issue with windows 7 in alpha snaps

Brian's Mail list account
 

What seems to be happening is an apparent random refresh of the page or screen being read by automatic say all, say an email, a web page a document,which stops the reading and you ar back at the start.
Its seemingly random, which makes it very hard to actually catch in the act. I'm just asking others to be aware and not if they get it. It may occur in Windows 10 but I've not tested it. It has been around for a while though, but as I say since its random, it seems not to happen a lot of the time as probably pages are too short. I am not talking about the refresh when some email readers get an email and the list updates, but an apparent random re read of desktop or page of text or just a stopping of a say all.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

Notice: handing maintenance of various add-ons of mine to the community, effective February 1, 2020

 

Dear NVDA community,

 

After assessing my life situation and maintenance of fourteen add-ons (DictationBridge is the fourteenth), I hereby announce that, effective February 1, 2020, I’ll be handing over maintenance of various add-ons developed or maintained by me to the community at large. The following add-ons will be handed over to you all:

 

  • Easy Table Navigator
  • Golden Cursor
  • ObjPad
  • SystrayList

 

As for Screen Curtain, it’ll be retired soon; for DictationBridge, I had a discussion with project maintainers about my intentions.

 

I’ll maintain the below add-ons for now with help from the community, reasons being:

 

  • A companion NVDA pull request exists: Add-on Updater, Enhanced Touch Gestures, Object Location Tones, Windows 10 App Essentials
  • Certain features will be sent as future pull requests: Enhanced Touch Gestures, Windows 10 App Essentials
  • Plan is being developed to find a way to incorporate features into NVDA itself: Add-on Updater, Control Usage Assistant, Enhanced Touch Gestures, Windows 10 App Essentials
  • Code maintenance: GoldWave, Resource Monitor, StationPlaylist

 

Of these, Windows 10 App Essentials is perhaps the most complex add-on – not because of code size and coverage, but because it is extremely sensitive to changes to NVDA screen reader source code and Windows 10 ecosystem. This is more so now as some of the most prominent (and powerful) features of this add-on – namely volume meter progress bar bug fix for Version 1803 and recognizing modern keyboard in Version 1903 and later is now part of NVDA screen reader itself, making it a bit hard to maintain support for really ancient NVDA releases. I can safely say now that, given continued transfer of code from Windows 10 App Essentials to NVDA, there will come a day when Windows 10 App Essentials, too, will go out the pasture, but that’s a long time away; as long as there is room to improve Windows 10 and its accessibility, along with finding ways to contribute to making NVDA more versatile in handling these issues without help from this add-on, I will continue to develop this add-on (and to answer a Twitter question from an NVDA user, part of the reason why I release dev snapshots of this add-on on a weekly basis is precisely due to the fact that Windows 10 will continue to show us ways to improve accessibility of apps, even ones coming from Microsoft; I know I sound angry and I am indeed angry about this issue, hence my love/hate relationship with this add-on; I’ll reserve a thread on add-ons mailing list to showcase frustrations with Windows 10 ecosystem and accessibility).

 

On a more optimistic note, I’m glad to see that some folks are offering to maintain at least Golden Cursor, and we had a discussion about Easy Table Navigator and making it more useful. I hope the same can be said about other add-ons I’m handing to the community in February.

 

Thank you.

Cheers,

Joseph

Re: Joseph Lee's add-ons: transition maintenance mode for stable add-ons, dev snapshots to require NVDA 2019.3 in any form after NVDACon 2019

Brian's Mail list account
 

This must be giving add on authors a massive pain in the brain right now.
I mean even add ons that have been converted , now seem to be not working in the latest Alpha. No not seen any announcement about betas being updated. I think it would be nice if this could be posted widely to let the general user find out now which add ons do not work any more, before the time gets too close to the update, since we have Christmas and new year and that will obviously distract a lot of us away from testing.

Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "Joseph Lee" <@joslee>
To: <nvda-devel@groups.io>
Sent: Monday, November 11, 2019 9:09 AM
Subject: [nvda-devel] Joseph Lee's add-ons: transition maintenance mode for stable add-ons, dev snapshots to require NVDA 2019.3 in any form after NVDACon 2019


Dear NVDA developers and add-ons community,



People who are keeping an eye on NVDA source code changes may have noticed
the following: as of November 11, 2019, beta branch is powered by Python 3.
This usually takes place before arrival of public betas by a few days to
weeks. I'll provide guidance for add-ons community once NVDA 2019.3 beta 1
is tagged.



In regards to my add-ons, the following is in effect or will go into effect
shortly after NVDACon 2019 (November 15-16, 2019):



Python 3 strict builds will go mainstream after NVDACon 2019, rolling out to
everyone by February 2020: for now anyone wishing to use an add-on that is
marked as "Python 3 strict" must download them from my website. Shortly
after NVDACon 2019, my add-ons will move to strictly Python 3, beginning
with development snapshots for certain add-ons (mostly StationPlaylist and
Windows 10 App Essentials). Over the next few weeks, Python 3 builds will
gradually show up on other update channels, ending with an add-on release by
late January 2020 (so by February 2020, all of my add-ons will require NVDA
2019.3.). This timetable is subject to change depending on when NVDA 2019.3
stable version is released.



Stable add-ons are in transition maintenance mode, effective immediately:
currently stable versions of my add-ons are written in a mixture of old and
new code in order to maximize compatibility - this means it works with NVDA
2019.3, too. In order to concentrate on gathering feedback on Python 3
builds of add-ons, I'll be suspending adding new features to stable add-ons
- that is, until a given add-on is powered by Python 3, only bug fixes and
localization updates will be seen on almost all of my add-ons (exceptions
include Add-on Updater and Windows 10 App Essentials).



During transition maintenance mode, version numbers will be based on latest
major release i.e. for StationPlaylist, you'll see 19.11.3 and 19.11.4 in
December (if they are ever released). In other words, there will be no
version 19.12 i.e. no major release in December 2019.



To summarize:



* Any stable add-on releases from me scheduled for 2019 are compatible
with old and new releases.
* Anything stable to be released from me on January 1, 2020 and later
will require NVDA 2019.3.
* If you are using development snapshots of my add-ons, Python 3 build
switchover is just a few days away: shortly after NVDACon 2019. If you
absolutely need to use NVDA 2019.2.1 or earlier (including due to
incompatible add-ons in NVDA 2019.3 of any form), PLEASE SWITCH TO STABLE
UPDATE CHANNEL TODAY! To do so, for any add-on you need to use in stable
form, go to NVDA menu/Preferences/Settings/Add-on Updater, and uncheck the
checkboxes for add-ons under "prefer development releases" list; if you are
not using Add-on Updater, don't worry.





Re: Plugin Help please!

Nathaniel Schmidt
 

Hi Derek,

I found out about the location of your modifications to latex-access after I had migrated my own copy of the code to Github.  we might try to find a way of integrating your code later on.  Currently, there are some other priorities at the forefront.  Thanks for checking in.

Nathaniel Schmidt

7

On 10 Nov 2019, at 6:56 pm, derek riemer <driemer.riemer@...> wrote:


I completely revamped your addon. https://github.com/derekriemer/latex-access-matrix Feel free to ask any  questions you have and/or send pull requests. We might try to get this into latex-access. The matrix browser has been completely rewritten. Also, I redid the key bindings. Why exactly do you want this to be an appModule? That'll prevent it from loading in any location, limiting the usage to only a specific text editor. It's completely reasonable to expect users to want to use this in a web browser.


On Wed, Nov 6, 2019 at 5:29 AM Julien Cochuyt <j.cochuyt@...> wrote:
Dear Nathaniel,

Count me in as well, but on the technical side.
First step would be to create a new github repo and import in it the latest svn from sourceforge.
Then, in a dedicated branch, any changes you made so far to try to make it work on newer NVDA.
Then, I guess, open the wiki section to Daniel's work on specifications?
Can you handle this or do you want I handle setting this up on my side and give you access?

Also, although a notepad appModule might be convenient for testing in earlier stages, I may have other practical solutions to propose for the real thing, such as an appModule overlay you can activate on any content/editor using global gestures.

Best regards,

Julien Cochuyt
Accessolutions


Le mer. 6 nov. 2019 à 12:50, Nathaniel Schmidt <schmidty2244@...> a écrit :
Hi David,

Thank you for your message and keen interest.  I hope this project can ultimately help you in your work and make it easier.  I only have a mild-to-moderate level of knowledge concerning the python language, so there will be a bit of a limit as to what I can actually achieve.  if you would like to discuss anything further then you can do so privately by emailing: schmidty2244@....

Kind regards,

Nathaniel Schmidt

7

On 6 Nov 2019, at 11:32 am, David Moore <jesusloves1966@...> wrote:



Hi Nathaniel!

My name is David Moore, and I tutor math quite a bit!

I type math and read math using LaTeX all of the time!

What you have mentioned with this add-on would help me so very much!

I no nothing about python, and could not contribute to the coding, but I would really like to work hand and hand with the person who would take the coding on, and I would like to work with that person to let them know just what the add-on should be able to do.

I am math all the way lOL!

And would be very interested in working with someone to update and add to this add-on!

Please email me, Nathaniel, or anyone else who wants to email me!

MY email is:
jesusloves1966@...

This is the most exciting NVDA news I have seen in a long time!

I hope I receive some messages from some people!

I work a lot with series notation, and a lot of calculus expressions.

Have a great day!

David Moore

 

Sent from Mail for Windows 10

 

From: Nathaniel Schmidt
Sent: Tuesday, November 5, 2019 6:02 AM
To: nvda-devel@groups.io; nvda-addons@groups.io
Subject: [nvda-devel] Plugin Help please!

 

Hi all,

 

If anyone can help, I would be grateful.  I am currently trying to update some plugin code I wrote the bulk of back in 2011, periodically updating it with a couple of other contributors up until about 2014.  I am hoping to ultimately package it as an addon and submit it to the community page, in the hope that people may find it useful.  I stopped coding while I was doing undergrad studies so I am a bit out-of-practice.  The plugin used to work with earlier versions of NVDA but no longer does.  In the past it has been used by at least two other people that I know of apart from myself (one of them may still be on the nvda-dev mailing list), so I feel that it may be a reasonable coding courtesy to try to update the code as much as possible, though it is no longer useful to me personally.  So won't be too worried if problems cannot be overcome.  FYI, I am using Windows 10 with NVDA 2019.2.1, Python 3.8 and comtypes 1.1.7.

 

The plugin was initially a global plugin (an admittedly sloppy but superficially convenient choice for its purposes) that would use registered COM objects, allowing Windows screen-readers to communicate with a cross-platform Python package called Latex-Access, developed by Alastair Irving at http://latex-access.sourceforge.net/.  The package's main purpose is to translate lines of LaTeX syntax into Nemeth and UEB Braille, as well as speech, making it quicker and easier to read and understand equations and expressions.  It also contains a matrix browser for viewing matrices in a table-like fashion.  In addition, it contains a preprocessor for interpreting and expressing custom-defined LaTeX expressions.  It would be somewhat useful for those studying, or teaching, mathematics at a secondary or tertiary educational level and who use the LaTeX document preparation system for their work, or reviewing the work of others.

 

The final checked-out file in Subversion is not up-to-date, as the project manager seems to have potentially gone off the grid and I can no longer remember the password to my old SourceForge account attached to my old email, so I am unable to make commits.  So a Dropbox link is below:

https://www.dropbox.com/s/a5qqiu6abgu7ekn/notepad.py?dl=0

 

The plugin is in the process of being ported from a global plugin to an app module, which an end-user should be able to rename at their leisure, to the executable file of any text-editor of their choice.  This should mostly be a smooth transition in each instance, as the scripts are designed to work within accessible edit controls.  Currently the plugin only supports controls which notify of text selection changes but this could be altered in future.  I realise that some of the key bindings are likely to clash with commands from other editors; I am happy to change them for the community but for now, the primary desire has been to stick with the conventions subjectively, implicitly set out by the project manager who wrote the JAWS scripts.  To keep things simple, I have set the appModule to use notepad.

 

The problem currently at the forefront is unintended and unexplained triggering of scripts.  One in particular, "script_inputMatrix", is causing havoc by being triggered by just about every possible keypress relevant to typing input and I am struggling to trace the exact cause of the problem.  The debug log output is as follows:

 

---Start---

IO - inputCore.InputManager.executeGesture (15:46:18.426):

Input: kb(laptop):control+m

ERROR - core.CorePump.run (15:46:18.454):

errors in this core pump cycle

Traceback (most recent call last):

  File "core.pyo", line 489, in run

  File "IAccessibleHandler.pyo", line 903, in pumpAll

  File "IAccessibleHandler.pyo", line 620, in processGenericWinEvent

  File "appModuleHandler.pyo", line 134, in update

  File "appModuleHandler.pyo", line 119, in getAppModuleFromProcessID

  File "appModuleHandler.pyo", line 97, in getAppNameFromProcessID

  File "C:\Users\natha\AppData\Roaming\nvda\scratchpad\appModules\notepad.py", line 190

    ui.message (_(msg))

     ^

SyntaxError: invalid syntax

DEBUGWARNING - NVDAObjects.UIA.UIA._prefetchUIACacheForPropertyIDs (15:46:19.369):

IUIAutomationElement.buildUpdatedCache failed given IDs of set([30019, 30022, 30086, 30025, 30036, 30070, 30103, 30008, 30009, 30010, 30046, 30079])

---End---

 

Sometimes the same error repeats twice with only one keypress but I have no idea why.  I have two questions resulting from this output:

 

(1) What, precisely, is the syntax error? I feel stupid in asking but I can't figure it out.  I’m sure it's probably right in front of me.  The only thing that springs to mind is that maybe the gettext function has trouble with the explicit call to the str class, forcing some integers to be converted to strings but that is not exactly a syntax error.

 

(2) The general flow of the debug log (especially consecutive occurrences of the same error after general input and output) tells me that the script in question is being categorically triggered after just about every keypress.  How and why could this be happening? Is there something wrong in the appModules subclass method of EditableText._caretScriptPostMovedHelper? I fully realise that python does not call methods of the same name in bass classes unless the subclass explicitly calls them; however, I do not see how this makes a difference in this instance because I have rehashed all of the code anyway and have placed my own code inside it.

 

Is anyone willing or able to help me with this dilemma? If anyone wants to use the latex-access scripts with Python 3 then in order to register the COM objects, you will have to go into preprocessor.py and enclose the statement "import cPickle as pickle" with the following:

---Start---

try:

                import cPickle as pickle

except:

                import pickle

---End---

Python 3 tries to automatically load the accelerator module first so one cannot explicitly call the faster module written in C.

 

Also, as an aside, I know that Braille support is currently rather primitive.  I don’t really understand the brailleHandler code at the moment, so my capacity to manipulate its data is quite limited.

 

Thanks in advance and kind regards,

 

Nathaniel Schmidt

 

<C783F415002B425D8EBADD5BFB39D94D.png>



--
Derek Riemer
Improving the world one byte at a time!        ⠠⠊⠍⠏⠗⠕⠧⠬ ⠮ ⠸⠺ ⠐⠕ ⠃⠽⠞⠑ ⠁⠞ ⠁ ⠐⠞⠖
•    Accessibility enthusiast.
•    Proud user of the NVDA screen reader.
•    Open source enthusiast.
•    Skier.

•    Personal website: https://derekriemer.com




Re: Joseph Lee's add-ons: transition maintenance mode for stable add-ons, dev snapshots to require NVDA 2019.3 in any form after NVDACon 2019

 

Hi,

Somehow pressed Contorl+Enter by accident…

Continuing from the note below:

Special notice for Screen Curtain add-on users: effective November 15, 2019, this add-on will be deprecated – no more releases from me. This add-on will be retired the day NVDA 2019.3 stable version is released.

 

Reminder for Golden Cursor and SystrayList add-on users: there will be one more (and major) release of these add-ons from me before I hand over maintenance of these add-ons to the community. These final releases will indeed require NVDA 2019.3.

 

If you have any questions, feel free to contact me via various means (email, Facebook, Twitter, etc.). Also, if you’re coming to my informal ad-don users meeting at NVDACon 2019, I’ll spend some time going over what I outlined in this email thread.

Thanks.

Cheers,

Joseph

 

 

From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Joseph Lee via Groups.Io
Sent: Monday, November 11, 2019 1:10 AM
To: nvda-devel@groups.io
Subject: [nvda-devel] Joseph Lee's add-ons: transition maintenance mode for stable add-ons, dev snapshots to require NVDA 2019.3 in any form after NVDACon 2019

 

Dear NVDA developers and add-ons community,

 

People who are keeping an eye on NVDA source code changes may have noticed the following: as of November 11, 2019, beta branch is powered by Python 3. This usually takes place before arrival of public betas by a few days to weeks. I’ll provide guidance for add-ons community once NVDA 2019.3 beta 1 is tagged.

 

In regards to my add-ons, the following is in effect or will go into effect shortly after NVDACon 2019 (November 15-16, 2019):

 

Python 3 strict builds will go mainstream after NVDACon 2019, rolling out to everyone by February 2020: for now anyone wishing to use an add-on that is marked as “Python 3 strict” must download them from my website. Shortly after NVDACon 2019, my add-ons will move to strictly Python 3, beginning with development snapshots for certain add-ons (mostly StationPlaylist and Windows 10 App Essentials). Over the next few weeks, Python 3 builds will gradually show up on other update channels, ending with an add-on release by late January 2020 (so by February 2020, all of my add-ons will require NVDA 2019.3.). This timetable is subject to change depending on when NVDA 2019.3 stable version is released.

 

Stable add-ons are in transition maintenance mode, effective immediately: currently stable versions of my add-ons are written in a mixture of old and new code in order to maximize compatibility – this means it works with NVDA 2019.3, too. In order to concentrate on gathering feedback on Python 3 builds of add-ons, I’ll be suspending adding new features to stable add-ons – that is, until a given add-on is powered by Python 3, only bug fixes and localization updates will be seen on almost all of my add-ons (exceptions include Add-on Updater and Windows 10 App Essentials).

 

During transition maintenance mode, version numbers will be based on latest major release i.e. for StationPlaylist, you’ll see 19.11.3 and 19.11.4 in December (if they are ever released). In other words, there will be no version 19.12 i.e. no major release in December 2019.

 

To summarize:

 

  • Any stable add-on releases from me scheduled for 2019 are compatible with old and new releases.
  • Anything stable to be released from me on January 1, 2020 and later will require NVDA 2019.3.
  • If you are using development snapshots of my add-ons, Python 3 build switchover is just a few days away: shortly after NVDACon 2019. If you absolutely need to use NVDA 2019.2.1 or earlier (including due to incompatible add-ons in NVDA 2019.3 of any form), PLEASE SWITCH TO STABLE UPDATE CHANNEL TODAY! To do so, for any add-on you need to use in stable form, go to NVDA menu/Preferences/Settings/Add-on Updater, and uncheck the checkboxes for add-ons under “prefer development releases” list; if you are not using Add-on Updater, don’t worry.

 

Joseph Lee's add-ons: transition maintenance mode for stable add-ons, dev snapshots to require NVDA 2019.3 in any form after NVDACon 2019

 

Dear NVDA developers and add-ons community,

 

People who are keeping an eye on NVDA source code changes may have noticed the following: as of November 11, 2019, beta branch is powered by Python 3. This usually takes place before arrival of public betas by a few days to weeks. I’ll provide guidance for add-ons community once NVDA 2019.3 beta 1 is tagged.

 

In regards to my add-ons, the following is in effect or will go into effect shortly after NVDACon 2019 (November 15-16, 2019):

 

Python 3 strict builds will go mainstream after NVDACon 2019, rolling out to everyone by February 2020: for now anyone wishing to use an add-on that is marked as “Python 3 strict” must download them from my website. Shortly after NVDACon 2019, my add-ons will move to strictly Python 3, beginning with development snapshots for certain add-ons (mostly StationPlaylist and Windows 10 App Essentials). Over the next few weeks, Python 3 builds will gradually show up on other update channels, ending with an add-on release by late January 2020 (so by February 2020, all of my add-ons will require NVDA 2019.3.). This timetable is subject to change depending on when NVDA 2019.3 stable version is released.

 

Stable add-ons are in transition maintenance mode, effective immediately: currently stable versions of my add-ons are written in a mixture of old and new code in order to maximize compatibility – this means it works with NVDA 2019.3, too. In order to concentrate on gathering feedback on Python 3 builds of add-ons, I’ll be suspending adding new features to stable add-ons – that is, until a given add-on is powered by Python 3, only bug fixes and localization updates will be seen on almost all of my add-ons (exceptions include Add-on Updater and Windows 10 App Essentials).

 

During transition maintenance mode, version numbers will be based on latest major release i.e. for StationPlaylist, you’ll see 19.11.3 and 19.11.4 in December (if they are ever released). In other words, there will be no version 19.12 i.e. no major release in December 2019.

 

To summarize:

 

  • Any stable add-on releases from me scheduled for 2019 are compatible with old and new releases.
  • Anything stable to be released from me on January 1, 2020 and later will require NVDA 2019.3.
  • If you are using development snapshots of my add-ons, Python 3 build switchover is just a few days away: shortly after NVDACon 2019. If you absolutely need to use NVDA 2019.2.1 or earlier (including due to incompatible add-ons in NVDA 2019.3 of any form), PLEASE SWITCH TO STABLE UPDATE CHANNEL TODAY! To do so, for any add-on you need to use in stable form, go to NVDA menu/Preferences/Settings/Add-on Updater, and uncheck the checkboxes for add-ons under “prefer development releases” list; if you are not using Add-on Updater, don’t worry.

 

Re: latest alpha and Outlook 365 message flags

Brian's Mail list account
 

It seems there are some oddities generally. I wonder if its got anything to do with other common software on the systems involved?
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "David Moore" <jesusloves1966@...>
To: <nvda-devel@groups.io>
Sent: Monday, November 11, 2019 2:24 AM
Subject: Re: [nvda-devel] latest alpha and Outlook 365 message flags


I am using the latest alpha snapshots on both on my laptops, and it works very well on both!
It must be something with your system!
David Moore

Sent from Mail for Windows 10

From: Lukasz Golonka
Sent: Sunday, November 10, 2019 5:28 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] latest alpha and Outlook 365 message flags

On Sun, 10 Nov 2019 19:51:28 -0000
"Brian's Mail list account via Groups.Io" <bglists=blueyonder.co.uk@groups.io> wrote:

There do seem to be other weird quirks in the alpha branch, like all the buttons in superantispyware no longer having any text but button, when in 2019.2.1 you can hear what they do.

This one was discussed previously, and for other users it works
correctly on both Windows 10 and 7. It looks like something is wrong on
your system.

Re: latest alpha and Outlook 365 message flags

Brian's Mail list account
 

No not here, or on two other machines, all do the same thing.

I cannot imagine what the differences might be, and if it were my system it would not work on 2019.2.1 would it? That means some odd interaction between my systems and the latest alpha.

I'm not willing to do a clean install just now but that is the only thing I can think of since turning off add ons has no effect on than effect at all.
Very odd.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "Lukasz Golonka" <wulfryk1@...>
To: <nvda-devel@groups.io>
Sent: Sunday, November 10, 2019 10:28 PM
Subject: Re: [nvda-devel] latest alpha and Outlook 365 message flags


On Sun, 10 Nov 2019 19:51:28 -0000
"Brian's Mail list account via Groups.Io" <bglists=blueyonder.co.uk@groups.io> wrote:

There do seem to be other weird quirks in the alpha branch, like all the buttons in superantispyware no longer having any text but button, when in 2019.2.1 you can hear what they do.

This one was discussed previously, and for other users it works
correctly on both Windows 10 and 7. It looks like something is wrong on
your system.



Re: latest alpha and Outlook 365 message flags

David Moore
 

I am using the latest alpha snapshots on both on my laptops, and it works very well on both!

It must be something with your system!

David Moore

 

Sent from Mail for Windows 10

 

From: Lukasz Golonka
Sent: Sunday, November 10, 2019 5:28 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] latest alpha and Outlook 365 message flags

 

On Sun, 10 Nov 2019 19:51:28 -0000

"Brian's Mail list account via Groups.Io" <bglists@...> wrote:

 

> There do seem to be other weird quirks in the alpha branch, like all the buttons in superantispyware no longer having any text but button, when in 2019.2.1 you can hear what they do.

 

 

This one was discussed previously, and for other users it works

correctly on both Windows 10 and 7. It looks like something is wrong on

your system.

 

 

 

 

 

Re: latest alpha and Outlook 365 message flags

Lukasz Golonka
 

On Sun, 10 Nov 2019 19:51:28 -0000
"Brian's Mail list account via Groups.Io" <bglists=blueyonder.co.uk@groups.io> wrote:

There do seem to be other weird quirks in the alpha branch, like all the buttons in superantispyware no longer having any text but button, when in 2019.2.1 you can hear what they do.

This one was discussed previously, and for other users it works
correctly on both Windows 10 and 7. It looks like something is wrong on
your system.

Re: latest alpha and Outlook 365 message flags

Lukasz Golonka
 

On Sun, 10 Nov 2019 21:08:48 +0100
"Ralf Kefferpuetz" <ralf.kefferpuetz@...> wrote:

Sure, it works with 2019.2.1 and all older versions of NVDA....

Could you please open an issue on GitHub then?

Re: latest alpha and Outlook 365 message flags

Ralf Kefferpuetz
 

Sure, it works with 2019.2.1 and all older versions of NVDA....

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Lukasz Golonka
Sent: Sonntag, 10. November 2019 16:47
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] latest alpha and Outlook 365 message flags

Hello,

On Sun, 10 Nov 2019 13:20:48 +0100
"Ralf Kefferpuetz" <ralf.kefferpuetz@...> wrote:

with latest alpha-19136,0124e647 without any addons and Office 365 (Microsoft® Outlook® for Office 365 MSO (16.0.12130.20232) 32-bit) in outlook the message flags are not spoken, like unread, forwarded, replied, replied all, attachments. This was in earlier alpha versions as well. Is that a known issue or is it just me?

In which version it last worked for you? Can you chec with 2019.2.1?
If it is working there, and not working in Alpha it is worth creating a bug report on GitHub.

--
Regards
Lukasz

Re: latest alpha and Outlook 365 message flags

Brian's Mail list account
 

There do seem to be other weird quirks in the alpha branch, like all the buttons in superantispyware no longer having any text but button, when in 2019.2.1 you can hear what they do.
Odd one that, but may, in the end be found to be different behaviour of patches in Python 3 not yet found and corrected.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "Lukasz Golonka" <wulfryk1@...>
To: <nvda-devel@groups.io>
Sent: Sunday, November 10, 2019 3:47 PM
Subject: Re: [nvda-devel] latest alpha and Outlook 365 message flags


Hello,

On Sun, 10 Nov 2019 13:20:48 +0100
"Ralf Kefferpuetz" <ralf.kefferpuetz@...> wrote:

with latest alpha-19136,0124e647 without any addons and Office 365 (Microsoft® Outlook® for Office 365 MSO (16.0.12130.20232) 32-bit) in outlook the message flags are not spoken, like unread, forwarded, replied, replied all, attachments. This was in earlier alpha versions as well. Is that a known issue or is it just me?

In which version it last worked for you? Can you chec with 2019.2.1?
If it is working there, and not working in Alpha it is worth creating
a bug report on GitHub.

--
Regards
Lukasz

Re: support for full screen applications in the terminal

Tage Johansson
 

Thanks for the suggestion.


The problem now is however that NVDA speaks "space" whenever I insert a character. I'm not sure why but I'm quite sure that it is not desired behaviour. Any suggestions or should I open an issue?


Best Regards,

Tage


On 11/10/2019 9:28 AM, derek riemer wrote:
You can set noru in vim to turn that annoying line marker off.

On Tue, Nov 5, 2019 at 7:28 PM Tony Malykh <anton.malykh@...> wrote:
I think that would be a great idea.

I've been mostly using emacs, and the experience is better than with
vim, although every now and then it does read some updates in the status
line, like line number changing, that is annoying.

I think that only constraining terminal updates to current line might
break some functionality - since in emacs there are useful status
updates appearing every now and then in the very last line of the
terminal. I think the best way would be to implement a feature to mark
certain areas of the terminal window as volatile and never speak updates
from them. Or maybe even automatically detect those areas, such as
status bars in vim and emacs, since I believe they are different in color...

--Tony

On 11/5/2019 4:12 AM, Tage Johansson wrote:
> Hi,
>
>
> I'm using the terminal alot and I've been using wsl (Windows Subsystem
> for Linux) quite heavily during the last year. I'm using NVDA with the
> linux terminal (started from cmd) and it works quite well. But it
> doesn't work that very well if I'm going to use a full screen
> application like vim.
>
>
> Vim is a powerful text editor running in the terminal. It displays the
> cursor position att the bottom of the screen. Since NVDA reads all
> changes in the current terminal window, the speech is interrupted when
> ever the cursor position changes. So when I type a character, NVDA
> does only speak the new cursor position which is quite annoying.
>
>
> Earlier, I've been using brltty on a pure linux machine. Brltty does
> only speak changes on the current line. That is mutch better when
> working with full screen applications like vim.
>
>
> Is it possible to let NVDA only speak changes on the current line? Or
> can I make an addon which enables that behaviour?
>
>
> Best regards,
>
> Tage
>
>
>
>
>





--
Derek Riemer
Improving the world one byte at a time!        ⠠⠊⠍⠏⠗⠕⠧⠬ ⠮ ⠸⠺ ⠐⠕ ⠃⠽⠞⠑ ⠁⠞ ⠁ ⠐⠞⠖
•    Accessibility enthusiast.
•    Proud user of the NVDA screen reader.
•    Open source enthusiast.
•    Skier.

•    Personal website: https://derekriemer.com




Re: latest alpha and Outlook 365 message flags

Lukasz Golonka
 

Hello,

On Sun, 10 Nov 2019 13:20:48 +0100
"Ralf Kefferpuetz" <ralf.kefferpuetz@...> wrote:

with latest alpha-19136,0124e647 without any addons and Office 365 (Microsoft® Outlook® for Office 365 MSO (16.0.12130.20232) 32-bit) in outlook the message flags are not spoken, like unread, forwarded, replied, replied all, attachments. This was in earlier alpha versions as well. Is that a known issue or is it just me?

In which version it last worked for you? Can you chec with 2019.2.1?
If it is working there, and not working in Alpha it is worth creating
a bug report on GitHub.

--
Regards
Lukasz

latest alpha and Outlook 365 message flags

Ralf Kefferpuetz
 

Hi all,

 

with latest alpha-19136,0124e647 without any addons and Office 365 (Microsoft® Outlook® for Office 365 MSO (16.0.12130.20232) 32-bit) in outlook the message flags are not spoken, like unread, forwarded, replied, replied all, attachments. This was in earlier alpha versions as well. Is that a known issue or is it just me?

 

Regards,

  Ralf

Re: support for full screen applications in the terminal

derek riemer
 

You can set noru in vim to turn that annoying line marker off.

On Tue, Nov 5, 2019 at 7:28 PM Tony Malykh <anton.malykh@...> wrote:
I think that would be a great idea.

I've been mostly using emacs, and the experience is better than with
vim, although every now and then it does read some updates in the status
line, like line number changing, that is annoying.

I think that only constraining terminal updates to current line might
break some functionality - since in emacs there are useful status
updates appearing every now and then in the very last line of the
terminal. I think the best way would be to implement a feature to mark
certain areas of the terminal window as volatile and never speak updates
from them. Or maybe even automatically detect those areas, such as
status bars in vim and emacs, since I believe they are different in color...

--Tony

On 11/5/2019 4:12 AM, Tage Johansson wrote:
> Hi,
>
>
> I'm using the terminal alot and I've been using wsl (Windows Subsystem
> for Linux) quite heavily during the last year. I'm using NVDA with the
> linux terminal (started from cmd) and it works quite well. But it
> doesn't work that very well if I'm going to use a full screen
> application like vim.
>
>
> Vim is a powerful text editor running in the terminal. It displays the
> cursor position att the bottom of the screen. Since NVDA reads all
> changes in the current terminal window, the speech is interrupted when
> ever the cursor position changes. So when I type a character, NVDA
> does only speak the new cursor position which is quite annoying.
>
>
> Earlier, I've been using brltty on a pure linux machine. Brltty does
> only speak changes on the current line. That is mutch better when
> working with full screen applications like vim.
>
>
> Is it possible to let NVDA only speak changes on the current line? Or
> can I make an addon which enables that behaviour?
>
>
> Best regards,
>
> Tage
>
>
>
>
>





--
Derek Riemer
Improving the world one byte at a time!        ⠠⠊⠍⠏⠗⠕⠧⠬ ⠮ ⠸⠺ ⠐⠕ ⠃⠽⠞⠑ ⠁⠞ ⠁ ⠐⠞⠖
•    Accessibility enthusiast.
•    Proud user of the NVDA screen reader.
•    Open source enthusiast.
•    Skier.

•    Personal website: https://derekriemer.com




Re: Latex-Access Development Update: Ported / Migrated to Git From SVN

derek riemer
 



On Wed, Nov 6, 2019 at 4:41 AM Nathaniel Schmidt <schmidty2244@...> wrote:
Hi all,

Since I am (a) getting bounce-backs from the original latex-access project manager’s email address; and (b) have received no response as of yet from the latex-access development mailing list, I have decided, for now, to take matters into my own hands.  I have migrated the source code repository from SVN on SourceForge to Git on GitHub, using Github's importing tool.  The code is licensed under NGPL2.0, so I see no problem with this.  If anyone wants push access then privately send me your GitHub username.  distributed version control is more pragmatically viable than centralised control anyway, allowing one to work off-line.  I have not changed the name spaces of authors in original SVN commits.  The project is small enough that any contributors could probably just collaborate with only the original master branch; however, if it gets more complicated than this, then since I am not terribly experienced with Git, I would prefer to work with a GitHub Flow branching strategy.  Note that this is very different from a GitFlow branching strategy.  Also, to keep things simple, I would probably want to work from a shared repository model, rather than fork-and-pull model.  In other words, I would strongly recommend that other users / contributors do not fork the online repository to their own Github account!  So I will probably either not except any pull-requests from forked repos, or if I do, I will only accept pull-requests from a forked repo if I can also be absolutely assured that the contributor‘s local master branch has been linked with the remote original master branch via the appropriate Git commands.  My moderate understanding and somewhat limited experience probably won’t cope with much beyond that…

Unfortunately, you're likely going to need to learn git. It's a very bad idea to let contributors  have access to your raw github repository, besides you and as small of a core userbase is necessary. It's not unlikely that someone will screw up and push things to master that they shouldn't and break you locally. This is why people use pull requests. If you don't take the time to learn this now, you'll likely find yourself dealing with a nasty merge conflict on local development later, or even worse, have a user purposefully or accidentally delete your master branch or corrupt it beyond repair, destroying anything you have lovally.

If anyone not experienced with version control systems or software development needs further help or clarification for anything, then let me know.  Repo can be cloned at.
https://github.com/SugarCaneNS/latex-access.git

Kind regards,

Nathaniel Schmidt

7




--
Derek Riemer
Improving the world one byte at a time!        ⠠⠊⠍⠏⠗⠕⠧⠬ ⠮ ⠸⠺ ⠐⠕ ⠃⠽⠞⠑ ⠁⠞ ⠁ ⠐⠞⠖
•    Accessibility enthusiast.
•    Proud user of the NVDA screen reader.
•    Open source enthusiast.
•    Skier.

•    Personal website: https://derekriemer.com




Re: Plugin Help please!

derek riemer
 

I completely revamped your addon. https://github.com/derekriemer/latex-access-matrix Feel free to ask any  questions you have and/or send pull requests. We might try to get this into latex-access. The matrix browser has been completely rewritten. Also, I redid the key bindings. Why exactly do you want this to be an appModule? That'll prevent it from loading in any location, limiting the usage to only a specific text editor. It's completely reasonable to expect users to want to use this in a web browser.


On Wed, Nov 6, 2019 at 5:29 AM Julien Cochuyt <j.cochuyt@...> wrote:
Dear Nathaniel,

Count me in as well, but on the technical side.
First step would be to create a new github repo and import in it the latest svn from sourceforge.
Then, in a dedicated branch, any changes you made so far to try to make it work on newer NVDA.
Then, I guess, open the wiki section to Daniel's work on specifications?
Can you handle this or do you want I handle setting this up on my side and give you access?

Also, although a notepad appModule might be convenient for testing in earlier stages, I may have other practical solutions to propose for the real thing, such as an appModule overlay you can activate on any content/editor using global gestures.

Best regards,

Julien Cochuyt
Accessolutions


Le mer. 6 nov. 2019 à 12:50, Nathaniel Schmidt <schmidty2244@...> a écrit :
Hi David,

Thank you for your message and keen interest.  I hope this project can ultimately help you in your work and make it easier.  I only have a mild-to-moderate level of knowledge concerning the python language, so there will be a bit of a limit as to what I can actually achieve.  if you would like to discuss anything further then you can do so privately by emailing: schmidty2244@....

Kind regards,

Nathaniel Schmidt

7

On 6 Nov 2019, at 11:32 am, David Moore <jesusloves1966@...> wrote:



Hi Nathaniel!

My name is David Moore, and I tutor math quite a bit!

I type math and read math using LaTeX all of the time!

What you have mentioned with this add-on would help me so very much!

I no nothing about python, and could not contribute to the coding, but I would really like to work hand and hand with the person who would take the coding on, and I would like to work with that person to let them know just what the add-on should be able to do.

I am math all the way lOL!

And would be very interested in working with someone to update and add to this add-on!

Please email me, Nathaniel, or anyone else who wants to email me!

MY email is:
jesusloves1966@...

This is the most exciting NVDA news I have seen in a long time!

I hope I receive some messages from some people!

I work a lot with series notation, and a lot of calculus expressions.

Have a great day!

David Moore

 

Sent from Mail for Windows 10

 

From: Nathaniel Schmidt
Sent: Tuesday, November 5, 2019 6:02 AM
To: nvda-devel@groups.io; nvda-addons@groups.io
Subject: [nvda-devel] Plugin Help please!

 

Hi all,

 

If anyone can help, I would be grateful.  I am currently trying to update some plugin code I wrote the bulk of back in 2011, periodically updating it with a couple of other contributors up until about 2014.  I am hoping to ultimately package it as an addon and submit it to the community page, in the hope that people may find it useful.  I stopped coding while I was doing undergrad studies so I am a bit out-of-practice.  The plugin used to work with earlier versions of NVDA but no longer does.  In the past it has been used by at least two other people that I know of apart from myself (one of them may still be on the nvda-dev mailing list), so I feel that it may be a reasonable coding courtesy to try to update the code as much as possible, though it is no longer useful to me personally.  So won't be too worried if problems cannot be overcome.  FYI, I am using Windows 10 with NVDA 2019.2.1, Python 3.8 and comtypes 1.1.7.

 

The plugin was initially a global plugin (an admittedly sloppy but superficially convenient choice for its purposes) that would use registered COM objects, allowing Windows screen-readers to communicate with a cross-platform Python package called Latex-Access, developed by Alastair Irving at http://latex-access.sourceforge.net/.  The package's main purpose is to translate lines of LaTeX syntax into Nemeth and UEB Braille, as well as speech, making it quicker and easier to read and understand equations and expressions.  It also contains a matrix browser for viewing matrices in a table-like fashion.  In addition, it contains a preprocessor for interpreting and expressing custom-defined LaTeX expressions.  It would be somewhat useful for those studying, or teaching, mathematics at a secondary or tertiary educational level and who use the LaTeX document preparation system for their work, or reviewing the work of others.

 

The final checked-out file in Subversion is not up-to-date, as the project manager seems to have potentially gone off the grid and I can no longer remember the password to my old SourceForge account attached to my old email, so I am unable to make commits.  So a Dropbox link is below:

https://www.dropbox.com/s/a5qqiu6abgu7ekn/notepad.py?dl=0

 

The plugin is in the process of being ported from a global plugin to an app module, which an end-user should be able to rename at their leisure, to the executable file of any text-editor of their choice.  This should mostly be a smooth transition in each instance, as the scripts are designed to work within accessible edit controls.  Currently the plugin only supports controls which notify of text selection changes but this could be altered in future.  I realise that some of the key bindings are likely to clash with commands from other editors; I am happy to change them for the community but for now, the primary desire has been to stick with the conventions subjectively, implicitly set out by the project manager who wrote the JAWS scripts.  To keep things simple, I have set the appModule to use notepad.

 

The problem currently at the forefront is unintended and unexplained triggering of scripts.  One in particular, "script_inputMatrix", is causing havoc by being triggered by just about every possible keypress relevant to typing input and I am struggling to trace the exact cause of the problem.  The debug log output is as follows:

 

---Start---

IO - inputCore.InputManager.executeGesture (15:46:18.426):

Input: kb(laptop):control+m

ERROR - core.CorePump.run (15:46:18.454):

errors in this core pump cycle

Traceback (most recent call last):

  File "core.pyo", line 489, in run

  File "IAccessibleHandler.pyo", line 903, in pumpAll

  File "IAccessibleHandler.pyo", line 620, in processGenericWinEvent

  File "appModuleHandler.pyo", line 134, in update

  File "appModuleHandler.pyo", line 119, in getAppModuleFromProcessID

  File "appModuleHandler.pyo", line 97, in getAppNameFromProcessID

  File "C:\Users\natha\AppData\Roaming\nvda\scratchpad\appModules\notepad.py", line 190

    ui.message (_(msg))

     ^

SyntaxError: invalid syntax

DEBUGWARNING - NVDAObjects.UIA.UIA._prefetchUIACacheForPropertyIDs (15:46:19.369):

IUIAutomationElement.buildUpdatedCache failed given IDs of set([30019, 30022, 30086, 30025, 30036, 30070, 30103, 30008, 30009, 30010, 30046, 30079])

---End---

 

Sometimes the same error repeats twice with only one keypress but I have no idea why.  I have two questions resulting from this output:

 

(1) What, precisely, is the syntax error? I feel stupid in asking but I can't figure it out.  I’m sure it's probably right in front of me.  The only thing that springs to mind is that maybe the gettext function has trouble with the explicit call to the str class, forcing some integers to be converted to strings but that is not exactly a syntax error.

 

(2) The general flow of the debug log (especially consecutive occurrences of the same error after general input and output) tells me that the script in question is being categorically triggered after just about every keypress.  How and why could this be happening? Is there something wrong in the appModules subclass method of EditableText._caretScriptPostMovedHelper? I fully realise that python does not call methods of the same name in bass classes unless the subclass explicitly calls them; however, I do not see how this makes a difference in this instance because I have rehashed all of the code anyway and have placed my own code inside it.

 

Is anyone willing or able to help me with this dilemma? If anyone wants to use the latex-access scripts with Python 3 then in order to register the COM objects, you will have to go into preprocessor.py and enclose the statement "import cPickle as pickle" with the following:

---Start---

try:

                import cPickle as pickle

except:

                import pickle

---End---

Python 3 tries to automatically load the accelerator module first so one cannot explicitly call the faster module written in C.

 

Also, as an aside, I know that Braille support is currently rather primitive.  I don’t really understand the brailleHandler code at the moment, so my capacity to manipulate its data is quite limited.

 

Thanks in advance and kind regards,

 

Nathaniel Schmidt

 

<C783F415002B425D8EBADD5BFB39D94D.png>



--
Derek Riemer
Improving the world one byte at a time!        ⠠⠊⠍⠏⠗⠕⠧⠬ ⠮ ⠸⠺ ⠐⠕ ⠃⠽⠞⠑ ⠁⠞ ⠁ ⠐⠞⠖
•    Accessibility enthusiast.
•    Proud user of the NVDA screen reader.
•    Open source enthusiast.
•    Skier.

•    Personal website: https://derekriemer.com




Re: Backwards incompatible change notice: speech and braille - get*TextForProperties -> getProperties*

derek riemer
 

It's necessary for us to support things like certain speech related things like sounds for links, spelling error notifications in line, ...

On Fri, Nov 8, 2019 at 2:58 AM Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io> wrote:
I can confirm audio themes is, as it now fails to initialise as I posted
elsewhere. Is this just a tidy up of existing code, or for some future use
that needs this to be changed.
 Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users
----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@...>
To: <nvda-devel@groups.io>
Sent: Thursday, November 07, 2019 3:58 PM
Subject: [nvda-devel] Backwards incompatible change notice: speech and
braille - get*TextForProperties -> getProperties*


> Hi all,
>
>
>
> Yesterday a new speech sequence mechanism was incorporated into NVDA
> master
> (alpha) branch, and with it, function names have changed. So if your code
> (including add-ons) relies on the following functions, please change it
> now:
>
>
>
> * speech.getSpeechTextForProperties -> speech.getPropertiesSpeech
> * braille.getBrailleTextForProperties -> braille.getPropertiesBraile
>
>
>
> For add-ons requiring NVDA 2019.3, go ahead and rename these functions in
> your modules. For ones needing to support NVDA 2019.2 and earlier, be sure
> to perform attribute checks (hasattr).
>
>
>
> The following add-ons are affected by this change:
>
>
>
> * AudioThemes
> * Windows 10 App Essentials
> * Possibly more
>
>
>
> Thank you.
>
> Cheers,
>
> Joseph
>
>
>
>
>






--
Derek Riemer
Improving the world one byte at a time!        ⠠⠊⠍⠏⠗⠕⠧⠬ ⠮ ⠸⠺ ⠐⠕ ⠃⠽⠞⠑ ⠁⠞ ⠁ ⠐⠞⠖
•    Accessibility enthusiast.
•    Proud user of the NVDA screen reader.
•    Open source enthusiast.
•    Skier.

•    Personal website: https://derekriemer.com