Pawel Urbanski wrote:

Unfortunately Pylance of VS Code kept throwing errors about missing
type when parsing the expression of:
self.appModule.InstanceVariableName

After glancing at your code briefly [1], it seems that what you are trying
to do
isn't to save runtime state data for an App Module, so much as you are
trying to
access the state of an App Module from an associated overlay class. Do I
understand that correctly?

I am no expert on overlay classes, nor how they are supposed to communicate

state, but I think a better way to do this might be by way of some global
namespace.
Fortunately, NVDA provides one of those, called globalVars.

You import globalVars in each of your modules, and then can set state upon
it,
and read state from it.

import globalVars
class AppModule(appModuleHandler.AppModule):
def __init__(self, *args, **kwargs):
# ...
globalVars.vscode = {}
globalVars.vscode["name"] = "myName"
# Or, if you don't need to bother with a dict
globalVars.vscodeName = "myName"

Then, in your other class, you can simply do:

if globalVars.vscodeName == "whatever":

There may be a more elegant way to reach outside the class scope to get at
the
AppModule's state variables from an overlay that also doesn't generate a
compiler error, but this is one that should definitely work and is easy to
read.

[1]:
https://github.com/accessifix/nvda-for-vs-code/releases/download/2022.1.0/nvda-for-vs-code-2022.1.0.nvda-addon

Luke

Are you going to release this on the community site, and do you need help
with
that?

Luke

Pawel Urbanski wrote:

Hi Everyone,
While nobody was interested to pick up developing the add-on, I
updated it to be compatible with new NVDA and and introduced some API
changes.
I do code things from time to time, so still have the need for this
add-on. The changes are not very signifficant, but I hope that for
those of you who use VS Code it is welcome news.
If time and life allow to do so, I hope to add some more features and
fixes - mainly about ergonomics and convenience.

You can find the updated add-on over here:
https://github.com/accessifix/nvda-for-vs-code/releases/tag/2022.1.0

Enjoy, happy hacking,
Pawel

Hi Everyone,
While nobody was interested to pick up developing the add-on, I
updated it to be compatible with new NVDA and and introduced some API
changes.
I do code things from time to time, so still have the need for this
add-on. The changes are not very signifficant, but I hope that for
those of you who use VS Code it is welcome news.
If time and life allow to do so, I hope to add some more features and
fixes - mainly about ergonomics and convenience.

You can find the updated add-on over here:
https://github.com/accessifix/nvda-for-vs-code/releases/tag/2022.1.0

Enjoy, happy hacking,
Pawel

If you have state that only needs to be utilised during the add-on's
runtime, and not persisted, I would just store it on the AppModule or
GlobalPlugin instance:

class AppModule(appModuleHandler.AppModule):
def __init__(self, *args, **kwargs):
super().__init__(*args, **kwargs)
self._someStateFlag = False
self._someOtherStateFlag = 14
# or
self._state = {'flag1': False, 'flag2': 14}

Is there a reason why this wouldn't be sufficient?

Regards,

James Scholes

On 21/06/2022 at 11:20, Pawel Urbanski wrote:

Dear Everyone,
Since I still occasionally use Visual Studio Code and nobody followed
up with my request to take over the development, I am working on
updating the add-on.
I am looking for hints and inspiration on how to best keep add-on
state. It does not need to be saved but needs to work when the
application is running. I use it to store some add-on flags and state.
Is there anything in NVDA api like this or maybe you cane up with a
working way to share global state. There is the configuration class
but I don't know if it can be made local to the add-on running
instance in the scope of the AppModule class - please treat this
example as explanatory not in terms of working code.

Thank you for any hints...
Pawel

Dear Everyone,
Since I still occasionally use Visual Studio Code and nobody followed
up with my request to take over the development, I am working on
updating the add-on.
I am looking for hints and inspiration on how to best keep add-on
state. It does not need to be saved but needs to work when the
application is running. I use it to store some add-on flags and state.
Is there anything in NVDA api like this or maybe you cane up with a
working way to share global state. There is the configuration class
but I don't know if it can be made local to the add-on running
instance in the scope of the AppModule class - please treat this
example as explanatory not in terms of working code.

Thank you for any hints...
Pawel

*******************
Text Analyzer Group
*******************



When editing a document using speech only, inconsistencies such as
unmatched parentheses, unintentional format changes, extra whitespace, and
stray or unspaced punctuation can often be missed. Text Analyzer is a tool
that notifies you of these errors in your document by using a spoken
message or WAV file. You can configure JAWS to announce discrepancies by
count, by description, or by sound while proofreading the document by
line, sentence, paragraph, or Say All command. Braille users will benefit
from this since a sound can be emitted before the user has time to read
the entire line looking for errors.



------------------------
Turning On Text Analyzer
------------------------



Text Analyzer is off by default. To turn it on, do one of the following:



* Use the layered keystroke, *INSERT+SPACEBAR* , *A*. By pressing and
releasing *INSERT+SPACEBAR* , and then pressing *A* , the Text Analyzer can
be toggled on or off.
* Open Settings Center ( *INSERT+F2* ). In the Search edit box type "text
analyzer" without the quotes. Press *DOWN ARROW* to move to Text Analyzer
in the filtered results. Press *SPACEBAR* to select an alert notification.

* Use Quick Settings ( *INSERT+V* ). The process for selecting an alert
notification is the same as the Settings Center procedure described above.





----------
Keystrokes
----------



If multiple issues are identified in the document, press *ALT+WINDOWS
Key+I* to move to the next item, or *ALT+SHIFT+WINDOWS Key+I* to move to
the previous item. Note that these keystrokes can still be used even if
Text Analyzer is off.



---------------------
Text Analyzer Options
---------------------



Use the radio buttons in this group to determine the type of alert used to
indicate errors when editing or proofreading a document by line, sentence,
paragraph, or Say All command. Select Indicate with Sound to play a WAV
file when a formatting error is detected. Select Speak Count to announce
the number of inconsistencies in the current text. Select Describe
Inconsistencies for a description of the error. The default setting is
off.



---------------------------
Indicate Mismatched Symbols
---------------------------



Select this check box to enable the detection of mismatched symbols such
as parenthesis, braces, brackets, angle brackets, and quotes. If this
check box is cleared, the items in the Symbols to Check group are not
available.



----------------
Symbols to Check
----------------



Select one or more check boxes to search for mismatched parentheses,
braces, brackets, angle brackets, or quotes where the equivalent opening
or closing symbol is missing. These check boxes are only available when
the Indicate Mismatched Symbols check box is selected.



------------------------
Inconsistencies to Check
------------------------



Select one or more check boxes to identify inconsistencies with stray
punctuation, extra spaces, missing capital letters, or inverted lowercase
and uppercase text.



---------------------
Font Changes to Check
---------------------



Select one or more check boxes to identify incorrect font changes in the
current text including name, size, attributes, and colors.

but that add-on you referrd, that is very huge and very detailed. It has too many features in it, I wish that add-on would be split up in different smaller
add-ons, though.

*******************
Text Analyzer Group
*******************



When editing a document using speech only, inconsistencies such as
unmatched parentheses, unintentional format changes, extra whitespace, and
stray or unspaced punctuation can often be missed. Text Analyzer is a tool
that notifies you of these errors in your document by using a spoken
message or WAV file. You can configure JAWS to announce discrepancies by
count, by description, or by sound while proofreading the document by
line, sentence, paragraph, or Say All command. Braille users will benefit
from this since a sound can be emitted before the user has time to read
the entire line looking for errors.



------------------------
Turning On Text Analyzer
------------------------



Text Analyzer is off by default. To turn it on, do one of the following:



* Use the layered keystroke, *INSERT+SPACEBAR* , *A*. By pressing and
releasing *INSERT+SPACEBAR* , and then pressing *A* , the Text Analyzer can
be toggled on or off.
* Open Settings Center ( *INSERT+F2* ). In the Search edit box type "text
analyzer" without the quotes. Press *DOWN ARROW* to move to Text Analyzer
in the filtered results. Press *SPACEBAR* to select an alert notification.

* Use Quick Settings ( *INSERT+V* ). The process for selecting an alert
notification is the same as the Settings Center procedure described above.





----------
Keystrokes
----------



If multiple issues are identified in the document, press *ALT+WINDOWS
Key+I* to move to the next item, or *ALT+SHIFT+WINDOWS Key+I* to move to
the previous item. Note that these keystrokes can still be used even if
Text Analyzer is off.



---------------------
Text Analyzer Options
---------------------



Use the radio buttons in this group to determine the type of alert used to
indicate errors when editing or proofreading a document by line, sentence,
paragraph, or Say All command. Select Indicate with Sound to play a WAV
file when a formatting error is detected. Select Speak Count to announce
the number of inconsistencies in the current text. Select Describe
Inconsistencies for a description of the error. The default setting is
off.



---------------------------
Indicate Mismatched Symbols
---------------------------



Select this check box to enable the detection of mismatched symbols such
as parenthesis, braces, brackets, angle brackets, and quotes. If this
check box is cleared, the items in the Symbols to Check group are not
available.



----------------
Symbols to Check
----------------



Select one or more check boxes to search for mismatched parentheses,
braces, brackets, angle brackets, or quotes where the equivalent opening
or closing symbol is missing. These check boxes are only available when
the Indicate Mismatched Symbols check box is selected.



------------------------
Inconsistencies to Check
------------------------



Select one or more check boxes to identify inconsistencies with stray
punctuation, extra spaces, missing capital letters, or inverted lowercase
and uppercase text.



---------------------
Font Changes to Check
---------------------



Select one or more check boxes to identify incorrect font changes in the
current text including name, size, attributes, and colors.

Sorry, but which last version?


I am using:

NVDA alpha-25623,1d24f9b0

Dropbox 150.4.5000


and the copy notiffications are announced by NVDA as normally...


The last version fo the add-on only announces the presence or absence of the Dropbox icon on systray and if it is there, can allso announce the status...


Best regards,

Rui Fontes
NVDA portuguese team




Às 09:35 de 20/06/2022, Brian's Mail list account via groups.io escreveu:

Not only those but the ding and alert copied to clipboard when you copy link to clipboard no longer is indicated in the latest version and current nvda.
Brian