Date   

Re: task manager addon

Doug Lee
 

"Fully accessible" is a bit subjective here perhaps. :-)

You can indeed navigate the Processes grid's first column just fine with Up and Down arrows; but checking
other columns seems to require object navigation, which makes skimming down, say, the CPU column very
inconvenient. This problem applies to other tabs as well, though I did not test all of them. These
difficulties are not unique to NVDA and are the result of the Task Manager's unusual UIA structure for some of
these grids.

On Wed, Sep 08, 2021 at 07:40:32PM +0200, René Linke wrote:
Hi,

On 08/09/2021 at 18:08, Dark Count wrote:
Has anybody come across an addon for task manager?
Why do you would need an add-on for that? It is fully accessible with NVDA
2021.1, at least in Windows 10 and Windows 11.

René

--
Doug Lee dgl@dlee.org http://www.dlee.org
Level Access doug.lee@LevelAccess.com http://www.LevelAccess.com
"It's not easy to be crafty and winsome at the same time, and few accomplish
it after the age of six." --John W. Gardner and Francesca Gardner Reese


Re: task manager addon

René Linke
 

Hi,

On 08/09/2021 at 18:08, Dark Count wrote:
Has anybody come across an addon for task manager?
Why do you would need an add-on for that? It is fully accessible with NVDA 2021.1, at least in Windows 10 and Windows 11.

René


Re: Clock add-on: current state, expect lots of changes in the next few days

Noelia Ruiz
 

Hello, additionally to Joseph explanation, I was requested to modernize my add-ons, by Cyrille and Lukasz, I think, to include the following features present in addonTemplate:

- Removal of color inversion in the stylesheet, to improve visual experience. This was added by Julien. Sorry since I am not sure how names and surnames are correctly spelled and I am from iPhone at this moment. - Since I use GitHub Actions, easier to set than Appveyor since this needs just to place yaml files on the github bar workflows without external services, I did things in a suboptimal way changing buildVars.py based on the pushed tag. And Lukasz make a pull request suggesting the correct change using the version parameter, that doesn"t need to change buildVars.py. So I have two actions: one for changing the version when pushing a tag, and the other one, to run on wolkflow dispatch event, which creates a tag and push it changing buildVars.py accordingly. Just to show that the version parameter is also an interesting feature of addonTemplate. About GitHub Actions, I wrote a wiki article based also on your Appveyor investigation, @Abdel. I am very grateful to Olexandr, author of unmute and checkGestures add-ons,  and Mesar, for their help on GitHub Actions too. But respecting the thread, addonTemplate allows to specify add-on versions without changing buildVars. Hope this helps.

Enviado desde mi iPhone

El 8 sept 2021, a las 18:42, Abdel <abdelkrim.bensaid@...> escribió:



Hi Joseph,

Thank you for this Clock add-on modernization initiative.

Kind regards,
Abdel.

Le 08/09/2021 à 16:24, Joseph Lee a écrit :

Hi,

Huge update: a fork of the Clock add-on was created under my account at:

https://github.com/josephsl/clock

If you want to see how add-ons are modernized, please watch the fork repo (mine). I plan to send the work to Abdel for inclusion in the future release.

Cheers,

Joseph

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Joseph Lee via groups.io
Sent: Wednesday, September 8, 2021 6:25 AM
To: nvda-addons@nvda-addons.groups.io
Subject: [nvda-addons] Clock add-on: current state, expect lots of changes in the next few days

 

Hello all,

The following notice is applicable to anyone using Clock add-on from Hrvoje Katic (perhaps a version of this notice should be sent to users list later):

A few weeks ago Hrvoje announced that he cannot maintain Clock add-on, and several people have stepped up to provide updates, including Abdel and Zvonimir. I was then asked to become a contributor to Clock add-on so the add-on can be modernized. Knowing that many of you rely on Clock add-on for various tasks, I decided to modernize the add-on on behalf of the community.

As part of add-on modernization, many changes will happen. First and foremost, the add-on will drop support for NVDA 2019.2.1 and earlier. Python 2 is end of life, and since 2020 many add-ons have migrated to Python 3. At the moment Clock add-on is one of those add-ons that will support older NVDA releases, but starting with a future version of the add-on, NVDA 2019.3 or later is required, preferably 2020.3 or later for best experience.

Second, localization and documentation will be updated. The latest localization data is from August 2020, and translators have provided updated localizations since then. One of the first tasks will be to acknowledge the hard work of translators by incorporating their latest work, as well as updating the add-on readme to fix possible grammar and spelling errors and to align the documentation with that of other add-ons.

Third, the latest community add-on template will be applied. Among other things, this means you must now use Python 3.7 or later to build the add-on, as well as providing Markdown extensions support.

Fourth, extensive code changes will occur. This mostly involves converting to Python 3 idioms, as well as performing lint and adding type annotations if needed. This change may also involve editing user interface messages to fix possible spelling and grammar issues.

I expect these tasks will take at least a week to complete. Although not set in stone, I hope to get the modernized (and upgraded) Clock add-on ready for release by late September after going through testing with other maintainers.

Also, if you are curious as to how to modernize an add-on for real, I suggest watching the following repository for the next few days:

https://github.com/hkatic/clock

My hope is that by watching this repository and looking at commit messages (and code changes), the community will get a sense of how to modernize add-ons.

Thank you.

Cheers,

Joseph


Re: number processing

Rui Fontes
 

Hello!


Download from:

https://nvda.es/files/get.php?file=numberprocessing


Best regards,

Rui Fontes
NVDA portuguese team


Às 17:14 de 08/09/2021, Dark Count escreveu:

Hello there.

A few weeks back somebody had a discussion about number processing with NVDA.

Is there an add on which gives the ability to change this?

Working with a student and they would like to have single digits for work instances, but this seems to be something not customizable in settings.

Perhaps a config file somewhere?


Thanks in advanced for suggestions.


D C






Re: Clock add-on: current state, expect lots of changes in the next few days

Abdel
 

Hi Joseph,

Thank you for this Clock add-on modernization initiative.

Kind regards,
Abdel.

Le 08/09/2021 à 16:24, Joseph Lee a écrit :

Hi,

Huge update: a fork of the Clock add-on was created under my account at:

https://github.com/josephsl/clock

If you want to see how add-ons are modernized, please watch the fork repo (mine). I plan to send the work to Abdel for inclusion in the future release.

Cheers,

Joseph

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Joseph Lee via groups.io
Sent: Wednesday, September 8, 2021 6:25 AM
To: nvda-addons@nvda-addons.groups.io
Subject: [nvda-addons] Clock add-on: current state, expect lots of changes in the next few days

 

Hello all,

The following notice is applicable to anyone using Clock add-on from Hrvoje Katic (perhaps a version of this notice should be sent to users list later):

A few weeks ago Hrvoje announced that he cannot maintain Clock add-on, and several people have stepped up to provide updates, including Abdel and Zvonimir. I was then asked to become a contributor to Clock add-on so the add-on can be modernized. Knowing that many of you rely on Clock add-on for various tasks, I decided to modernize the add-on on behalf of the community.

As part of add-on modernization, many changes will happen. First and foremost, the add-on will drop support for NVDA 2019.2.1 and earlier. Python 2 is end of life, and since 2020 many add-ons have migrated to Python 3. At the moment Clock add-on is one of those add-ons that will support older NVDA releases, but starting with a future version of the add-on, NVDA 2019.3 or later is required, preferably 2020.3 or later for best experience.

Second, localization and documentation will be updated. The latest localization data is from August 2020, and translators have provided updated localizations since then. One of the first tasks will be to acknowledge the hard work of translators by incorporating their latest work, as well as updating the add-on readme to fix possible grammar and spelling errors and to align the documentation with that of other add-ons.

Third, the latest community add-on template will be applied. Among other things, this means you must now use Python 3.7 or later to build the add-on, as well as providing Markdown extensions support.

Fourth, extensive code changes will occur. This mostly involves converting to Python 3 idioms, as well as performing lint and adding type annotations if needed. This change may also involve editing user interface messages to fix possible spelling and grammar issues.

I expect these tasks will take at least a week to complete. Although not set in stone, I hope to get the modernized (and upgraded) Clock add-on ready for release by late September after going through testing with other maintainers.

Also, if you are curious as to how to modernize an add-on for real, I suggest watching the following repository for the next few days:

https://github.com/hkatic/clock

My hope is that by watching this repository and looking at commit messages (and code changes), the community will get a sense of how to modernize add-ons.

Thank you.

Cheers,

Joseph


number processing

Dark Count
 

Hello there.

A few weeks back somebody had a discussion about number processing with NVDA.

Is there an add on which gives the ability to change this?

Working with a student and they would like to have single digits for work instances, but this seems to be something not customizable in settings.

Perhaps a config file somewhere?


Thanks in advanced for suggestions.


D C


task manager addon

Dark Count
 

Hello.

Has anybody come across an addon for task manager?


Thanks,


D C


Re: Clock add-on: current state, expect lots of changes in the next few days

 

Hi,

Huge update: a fork of the Clock add-on was created under my account at:

https://github.com/josephsl/clock

If you want to see how add-ons are modernized, please watch the fork repo (mine). I plan to send the work to Abdel for inclusion in the future release.

Cheers,

Joseph

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Joseph Lee via groups.io
Sent: Wednesday, September 8, 2021 6:25 AM
To: nvda-addons@nvda-addons.groups.io
Subject: [nvda-addons] Clock add-on: current state, expect lots of changes in the next few days

 

Hello all,

The following notice is applicable to anyone using Clock add-on from Hrvoje Katic (perhaps a version of this notice should be sent to users list later):

A few weeks ago Hrvoje announced that he cannot maintain Clock add-on, and several people have stepped up to provide updates, including Abdel and Zvonimir. I was then asked to become a contributor to Clock add-on so the add-on can be modernized. Knowing that many of you rely on Clock add-on for various tasks, I decided to modernize the add-on on behalf of the community.

As part of add-on modernization, many changes will happen. First and foremost, the add-on will drop support for NVDA 2019.2.1 and earlier. Python 2 is end of life, and since 2020 many add-ons have migrated to Python 3. At the moment Clock add-on is one of those add-ons that will support older NVDA releases, but starting with a future version of the add-on, NVDA 2019.3 or later is required, preferably 2020.3 or later for best experience.

Second, localization and documentation will be updated. The latest localization data is from August 2020, and translators have provided updated localizations since then. One of the first tasks will be to acknowledge the hard work of translators by incorporating their latest work, as well as updating the add-on readme to fix possible grammar and spelling errors and to align the documentation with that of other add-ons.

Third, the latest community add-on template will be applied. Among other things, this means you must now use Python 3.7 or later to build the add-on, as well as providing Markdown extensions support.

Fourth, extensive code changes will occur. This mostly involves converting to Python 3 idioms, as well as performing lint and adding type annotations if needed. This change may also involve editing user interface messages to fix possible spelling and grammar issues.

I expect these tasks will take at least a week to complete. Although not set in stone, I hope to get the modernized (and upgraded) Clock add-on ready for release by late September after going through testing with other maintainers.

Also, if you are curious as to how to modernize an add-on for real, I suggest watching the following repository for the next few days:

https://github.com/hkatic/clock

My hope is that by watching this repository and looking at commit messages (and code changes), the community will get a sense of how to modernize add-ons.

Thank you.

Cheers,

Joseph


Weather_Plus8.5 update available

Adriano Barbieri
 

Hi to every one,

Changes in this version:
• Fixed copy function of partial text selection using control + c, and enabled the home, end and pageup keys, pagedown in enabled windows.
• Correct response pressure in mmHg.
• Removed version number from readme.html
• Fixed a bug duringthe conversion of string to 24 hour format.
• Prevented fatal error if folder en is missing.
• Rain or snow probability percentages are now displayed only if their value is greater than zero.
• updated croatian locale translation (thanks to Tarik Hadžirovi).
• Added checks in case of empty list returned by the API response.
Thanks to Rui Fontes and Rémy Ruiz for maintaining and supporting Weather_Plus.

Repository:
https://github.com/ruifontes/Weather_Plus/

Download:

https://github.com/ruifontes/Weather_Plus/releases/download/8.5/Weather_Plus8.5.nvda-addon

Or:
https://www.nvda.it/files/plugin/weather_plus8.5.nvda-addon


Regards
Adriano


Clock add-on: current state, expect lots of changes in the next few days

 

Hello all,

The following notice is applicable to anyone using Clock add-on from Hrvoje Katic (perhaps a version of this notice should be sent to users list later):

A few weeks ago Hrvoje announced that he cannot maintain Clock add-on, and several people have stepped up to provide updates, including Abdel and Zvonimir. I was then asked to become a contributor to Clock add-on so the add-on can be modernized. Knowing that many of you rely on Clock add-on for various tasks, I decided to modernize the add-on on behalf of the community.

As part of add-on modernization, many changes will happen. First and foremost, the add-on will drop support for NVDA 2019.2.1 and earlier. Python 2 is end of life, and since 2020 many add-ons have migrated to Python 3. At the moment Clock add-on is one of those add-ons that will support older NVDA releases, but starting with a future version of the add-on, NVDA 2019.3 or later is required, preferably 2020.3 or later for best experience.

Second, localization and documentation will be updated. The latest localization data is from August 2020, and translators have provided updated localizations since then. One of the first tasks will be to acknowledge the hard work of translators by incorporating their latest work, as well as updating the add-on readme to fix possible grammar and spelling errors and to align the documentation with that of other add-ons.

Third, the latest community add-on template will be applied. Among other things, this means you must now use Python 3.7 or later to build the add-on, as well as providing Markdown extensions support.

Fourth, extensive code changes will occur. This mostly involves converting to Python 3 idioms, as well as performing lint and adding type annotations if needed. This change may also involve editing user interface messages to fix possible spelling and grammar issues.

I expect these tasks will take at least a week to complete. Although not set in stone, I hope to get the modernized (and upgraded) Clock add-on ready for release by late September after going through testing with other maintainers.

Also, if you are curious as to how to modernize an add-on for real, I suggest watching the following repository for the next few days:

https://github.com/hkatic/clock

My hope is that by watching this repository and looking at commit messages (and code changes), the community will get a sense of how to modernize add-ons.

Thank you.

Cheers,

Joseph


Re: [preview] Access8Math 3.1 - Export HTML display settings(math object using block/inline), LaTeX delimiter settings

Noelia Ruiz
 

Hello, NV Access has ownership of all repos in nvdaaddons organization, so we have to fork your repo and grant you write access, so you can send changes to stable branch when needed, and new messages can be included in the translations system. I"ll do changes today. I have just come back to home after job. Cheers

Enviado desde mi iPhone

El 7 sept 2021, a las 15:49, woody tseng <tsengwoody.tw@...> escribió:

Hello,

> If you agree and if you need assistance for this, I, Noelia or someone else can help; just ask!
I agree includ in translation system.
I created the stable branch According to the article
> nvaccessAuto should have permission to push to the stable branch.
Do I need to make settings in github for this step?

Woody


Re: [preview] Access8Math 3.1 - Export HTML display settings(math object using block/inline), LaTeX delimiter settings

woody tseng
 

Hello,

> If you agree and if you need assistance for this, I, Noelia or someone else can help; just ask!
I agree includ in translation system.
I created the stable branch According to the article
> nvaccessAuto should have permission to push to the stable branch.
Do I need to make settings in github for this step?

Woody


Re: [preview] Access8Math 3.1 - Export HTML display settings(math object using block/inline), LaTeX delimiter settings

Noelia Ruiz
 

Hello:

I agree with Zyrille. Here's useful info about how to include add-ons
in the translation system, in case you are interested:

https://github.com/nvaccess/mrconfig

Kind regards

2021-09-07 14:03 GMT+02:00, Cyrille via groups.io
<cyrille.bougot2=laposte.net@groups.io>:


Hello Woody

Thanks for this update.
I will try to provide an update of the French translation of this add-on;
not sure that this will be ready by the next weekend; so do not expect my PR
to hold the release.

The translation of this add-on is a lot of work.

As already done in the past, I would recommend to you to ask for the
integration of this add-on in the automatic translation framework. This
would ease the work of translators for the interface and the documentation
(doc\xx\readme.md, locale\xx\LC_MESSAGES\nvda.po,  locale\xx\manifest.ini).
Also, I guess that with slight code modification
globalPlugins\Access8Math\locale\about.txt could land in the nvda.po
messages and thus benefit the translation framework.

There would still remain the globalPlugins\Access8Math\locale\math.rule and
globalPlugins\Access8Math\locale\unicode.dic to be manually translated and
sent via PRs but this would already lessen the burdon of manual process.

Also, I have not provided the documentation in French (doc\fr\readme.md)
since the translation of the strings it contains is already done in on the
community website. I do not want to do this duplicated work of translation.
If you integrate the automatic translation framework, the add-on's
documentation will automatically generated for the add-on from the website's
page.

Would you reconsider including your add-on in the automatic translation
framework? That's a good timing for it since many bugs have been fixed by
Reef from NVAccess who is now quite reactive on this topic. And some add-ons
have been included recently.
If you agree and if you need assistance for this, I, Noelia or someone else
can help; just ask!

Cheers,

Cyrille


De : "woody tseng"
A : nvda-addons@nvda-addons.groups.io
Envoyé: mardi 7 Septembre 2021 13:10
Objet : [nvda-addons] [preview] Access8Math 3.1 - Export HTML display
settings(math object using block/inline), LaTeX delimiter settings

Hello,

NVDA 2021.2 RC has been released, Access8Math 3.1 is expected to be updated
next weekend, if there is a translation to be updated, it can be provided by
github PR(https://github.com/tsengwoody/Access8Math) or email before next
weekend

# Access8Math v3.1 Update

*    NVDA+ gestures enable option adjustment and can modify the shortcut
keys in the input gesture
*    HTML windows are now presented as virtual menu
*    Fixed an issue where the HTML view cannot be converted when text
include "`" character
*    When the number of words in the document is greater than 4096, the
content will not be converted to HTML view
*    Added mathematical set LaTeX commands
*    Update alt+m to insert "\(", "\)" LaTeX marks before and after the
currently selected text (when there is no selected text, it is the current
cursor position)
*    In the General settings, you can choose whether the math content in the
exported HTML is presented on a separate line(block/inline)
*    When exporting HTML, save the original text file in the compressed
file
*    In the general settings, you can choose to use bracket or money symbol
as the LaTeX delimiter

Access8Math 3.1 preview

Woody









Re: [preview] Access8Math 3.1 - Export HTML display settings(math object using block/inline), LaTeX delimiter settings

Cyrille
 

 
Hello Woody

Thanks for this update.
I will try to provide an update of the French translation of this add-on; not sure that this will be ready by the next weekend; so do not expect my PR to hold the release.

The translation of this add-on is a lot of work.

As already done in the past, I would recommend to you to ask for the integration of this add-on in the automatic translation framework. This would ease the work of translators for the interface and the documentation (doc\xx\readme.md, locale\xx\LC_MESSAGES\nvda.po,  locale\xx\manifest.ini).
Also, I guess that with slight code modification globalPlugins\Access8Math\locale\about.txt could land in the nvda.po messages and thus benefit the translation framework.

There would still remain the globalPlugins\Access8Math\locale\math.rule and globalPlugins\Access8Math\locale\unicode.dic to be manually translated and sent via PRs but this would already lessen the burdon of manual process.

Also, I have not provided the documentation in French (doc\fr\readme.md) since the translation of the strings it contains is already done in on the community website. I do not want to do this duplicated work of translation. If you integrate the automatic translation framework, the add-on's documentation will automatically generated for the add-on from the website's page.

Would you reconsider including your add-on in the automatic translation framework? That's a good timing for it since many bugs have been fixed by Reef from NVAccess who is now quite reactive on this topic. And some add-ons have been included recently.
If you agree and if you need assistance for this, I, Noelia or someone else can help; just ask!

Cheers,

Cyrille

 
De : "woody tseng"
A : nvda-addons@nvda-addons.groups.io
Envoyé: mardi 7 Septembre 2021 13:10
Objet : [nvda-addons] [preview] Access8Math 3.1 - Export HTML display settings(math object using block/inline), LaTeX delimiter settings
 
Hello,

NVDA 2021.2 RC has been released, Access8Math 3.1 is expected to be updated next weekend, if there is a translation to be updated, it can be provided by github PR(https://github.com/tsengwoody/Access8Math) or email before next weekend

# Access8Math v3.1 Update

*    NVDA+ gestures enable option adjustment and can modify the shortcut keys in the input gesture
*    HTML windows are now presented as virtual menu
*    Fixed an issue where the HTML view cannot be converted when text include "`" character
*    When the number of words in the document is greater than 4096, the content will not be converted to HTML view
*    Added mathematical set LaTeX commands
*    Update alt+m to insert "\(", "\)" LaTeX marks before and after the currently selected text (when there is no selected text, it is the current cursor position)
*    In the General settings, you can choose whether the math content in the exported HTML is presented on a separate line(block/inline)
*    When exporting HTML, save the original text file in the compressed file
*    In the general settings, you can choose to use bracket or money symbol as the LaTeX delimiter

Access8Math 3.1 preview

Woody


[preview] Access8Math 3.1 - Export HTML display settings(math object using block/inline), LaTeX delimiter settings

woody tseng
 

Hello,

NVDA 2021.2 RC has been released, Access8Math 3.1 is expected to be updated next weekend, if there is a translation to be updated, it can be provided by github PR(https://github.com/tsengwoody/Access8Math) or email before next weekend

# Access8Math v3.1 Update

*    NVDA+ gestures enable option adjustment and can modify the shortcut keys in the input gesture
*    HTML windows are now presented as virtual menu
*    Fixed an issue where the HTML view cannot be converted when text include "`" character
*    When the number of words in the document is greater than 4096, the content will not be converted to HTML view
*    Added mathematical set LaTeX commands
*    Update alt+m to insert "\(", "\)" LaTeX marks before and after the currently selected text (when there is no selected text, it is the current cursor position)
*    In the General settings, you can choose whether the math content in the exported HTML is presented on a separate line(block/inline)
*    When exporting HTML, save the original text file in the compressed file
*    In the general settings, you can choose to use bracket or money symbol as the LaTeX delimiter

Access8Math 3.1 preview

Woody


FW: [nvda-devel] NVDA 2021.2rc1 has been released

 

 

 

From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of sean@...
Sent: Monday, September 6, 2021 11:34 PM
To: nvda-devel@groups.io
Subject: [nvda-devel] NVDA 2021.2rc1 has been released

 

Hi all,

NVDA 2021.2rc1 has been released. This is a release candidate, and unless any critical issues are found, this will be identical to the 2021.2 release.

Highlights and download links can be found in the release blog post at: https://www.nvaccess.org/post/nvda-2021-2rc1/


Re: How to mute nvda?

Brian's Mail list account
 

I'd have thought that profiles might solve the problem as his add on is already. If the speak keys or whatever is turned off in the profile for the game executable it surely should work?
Brian

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

----- Original Message -----
From: "Noelia Ruiz" <nrm1977@gmail.com>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Monday, September 06, 2021 1:48 PM
Subject: Re: [nvda-addons] How to mute nvda?


Hello, this is related to an NVDA add-on, right?
Can you provide some piece of code to provide a clearer idea and try
to help you?
Cheers

2021-09-06 11:52 GMT+02:00, Han Solo <skydreamer2112@gmail.com>:
Hi!


I am writing a game in which I want the information to be spoken after
pressing the key, eg the x key says the coordinates, the g key the
amount of gold, etc. I use cytolk for the sound of the game. I say the
information with the command "tolk.output (" blebleble ") and everything
is OK, but the computer says the pressed key as well. I don't want it to
say the pressed key just to say my tolk.output.
How to do it?
regards









Re: How to mute nvda?

Noelia Ruiz
 

Hello, this is related to an NVDA add-on, right?
Can you provide some piece of code to provide a clearer idea and try
to help you?
Cheers

2021-09-06 11:52 GMT+02:00, Han Solo <skydreamer2112@gmail.com>:

Hi!


I am writing a game in which I want the information to be spoken after
pressing the key, eg the x key says the coordinates, the g key the
amount of gold, etc. I use cytolk for the sound of the game. I say the
information with the command "tolk.output (" blebleble ") and everything
is OK, but the computer says the pressed key as well. I don't want it to
say the pressed key just to say my tolk.output.
How to do it?
regards







How to mute nvda?

Han Solo
 

Hi!


I am writing a game in which I want the information to be spoken after pressing the key, eg the x key says the coordinates, the g key the amount of gold, etc. I use cytolk for the sound of the game. I say the information with the command "tolk.output (" blebleble ") and everything is OK, but the computer says the pressed key as well. I don't want it to say the pressed key just to say my tolk.output.
How to do it?
regards


Re: Visual Studio Add-on.

Noelia Ruiz
 

Hello. You posted to the add-ons mailing list.

To send a message to this group, send an email to

nvda-addons@nvda-addons.groups.io

Thanks

2021-09-05 13:57 GMT+02:00, Nguyễn Cường <banlinhdanong5004@gmail.com>:

Hi, can you ask about builgbox, lmms with NVDA? I don't know how to
post to the group.

2021-09-05 18:27 GMT+07:00, Pawel Urbanski <pawel@e-urbanski.com>:
Thank you for your message. I will be very happy to help with the
transfer and discuss what/if such or such faeture needs to be coded or
it can be replaced with more clever configuration.

On 04/09/2021, Paulius <paulius.leveris@gmail.com> wrote:
Hello mr. Pawel,
With a friend of mine, we recently became interested in
VisualStudioCode IDE and its ongoing developments in accessibility.
As we noticed some really useful features there are missing, I think
we would be able to maintain this add-on for a while.
If things go well, we plan to integrate the following features to be
used with this add-on:
* DocBlocAnnotation indents (a way of indents PHP programmers use in
developing APIPlatform applications);
* Announcements of line overflows.
We may come up with some other ideas in the future...
It's important to mention that VisualStudioCode accessibility is
improving really quite constantly and often; Lots of accessibility
issues reported to Microsoft are being fixed in a surprising manner,
but we still need to keep an eye on the incoming changes from time to
time. That's what we would be happy to do for now.

With that being said, I think I'd agree (even for a while) to have a
look to this add-on from time to time.

Thank you.
Best regards,
Paulius<div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br />
<table style="border-top: 1px solid #D3D4DE;">
<tr>
<td style="width: 55px; padding-top: 13px;"><a
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail"
target="_blank"><img
src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif"
alt="" width="46" height="29" style="width: 46px; height: 29px;"
/></a></td>
<td style="width: 470px; padding-top: 12px; color: #41424e;
font-size: 13px; font-family: Arial, Helvetica, sans-serif;
line-height: 18px;">Virus-free. <a
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail"
target="_blank" style="color: #4453ea;">www.avast.com</a>
</td>
</tr>
</table><a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1"
height="1"></a></div>

2021-09-04 22:46 GMT+03:00, Pawel Urbanski <pawel@e-urbanski.com>:
Hi Everyone,
While this message may be interesting to just a handful of people on
the list, it is the most convenient way for me to address the
following things:
** Since I am coding less and less or almost nothing in the regular
sense of the full-time developer, my needs have changed alot,
** Visual Studio Code is a very good tool for many things, including
code reviews, writing code obviously and so on,
** There are places where it could be moreverbose or provide some ways
to bridge the screen reader when in the debugging session, it is still
a very good tool,

Considering the points above I am looking for someone to transfer my
repository and to take over the development of the add-on.
** I will spend a few evenings getting the code more tidy, fixing 2
little bugs, which I finally solved after resorting to reading NVDA's
sources.
** I will send a handful of notes about day-to-day ergonomics to the
Visual Studio Code team with the hope they will consider them,
** The next add-on release will hopefully introduce a few simple
settings - time and energy allowing,
** I have a few ideas for the improvements, which I briefly mentioned
and will pass them along,

Unless there will be interest in taking over the development, Iwill
set the repository as either archived or add changes on a very likely
random occasions... The time frame for all the things I mentioned is
aproximately end of October.

All the best,
Pawel

















641 - 660 of 17482