Date   
Re: NVDA crashes if non-ASCII characters are in the path

Reef Turner
 

One possible work-around (that I don't like very much) would be to detect the crash conditions on start up (espeak synth, path with non-ASCII), warn the user and set a different synth.

-----Original Message-----
From: nvda-devel@groups.io On Behalf Of Nikita
Sent: Wednesday, 5 February 2020 7:38 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] NVDA crashes if non-ASCII characters are in the path

Unfortunately, this is a rather serious problem, the danger of which is probably underestimated.
Because of this problem, it is impossible to run new NVDA if the path to unpacked version contains non-ASCII characters.
As a result, inexperienced users may not understand why the new NVDA portable does not start.
There are Non-ASCII characters in languages based on the Latin alphabet, for example, French, German, Spanish. The so-called diacritics.
It is also bad that the log of NVDA does not contain any errors. NVDA crashes before it has time to write something.
This is an old bug that manifested even in Python 2 versions. That is not a problem of Python 3 migration.

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Brian's Mail list account via Groups.Io
Sent: Wednesday, February 05, 2020 8:54 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] NVDA crashes if non-ASCII characters are in the path

I wonder how many people this might affect? If somebody likes espeak, one supposes this will be people who use other languages than the Latin based ones with this synth. I could not see the issue on the Espeak mail list, so suspect its been around for a while. Could an older version be used to temporarily fix this as it might make some people not want to switch, assuming of course the problem is not already in the current stable python 2. I'd not know.

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: "Reef Turner" <reef@...>
To: <nvda-devel@groups.io>
Sent: Wednesday, February 05, 2020 9:10 AM
Subject: Re: [nvda-devel] NVDA crashes if non-ASCII characters are in the
path


Hi Nikita,

Thanks for pointing this out. It is a known issue [1]. We are confident this
is caused by an issue in espeak and there is little we can do about it in
the short term. We hope that the espeak maintainers will fix this issue, but
unfortunately it is too late for a fix to be included in 2019.3.

[1] https://github.com/nvaccess/nvda/issues/10607

Where is CapsLock management?

Alberto Buffolino
 

Hi,
I'm talking about NVDA sources and capsLock status management.
I'm quite sure to have seen it years ago, but I cannot find it today.
Where is it?
Thanks.
Alberto

Re: problems opening the task manager

Brian's Mail list account
 

Yes they certainly do. I just tried it I blame Microsoft buggy UIA as usual.
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" <dhf360@...>
To: "nvda-devel" <nvda-devel@groups.io>
Sent: Wednesday, February 05, 2020 11:10 PM
Subject: Re: [nvda-devel] problems opening the task manager


You're talking about the slow response when opening the task manager?
Its a very known issue, but some people thought that is not relevant to
solve. I installed the task manager of windows 7, where all the tings work
properly.

Regards,
David CM
Ingeniero en computación (ITCR)
[image: Experto certificado en NVDA.] <https://certification.nvaccess.org/>
correo: dhf360@...

Encuentra mis proyectos libres en github. <https://github.com/davidacm/>
y las publicaciones en mi canal de youtube.
<https://www.youtube.com/channel/UCYnnJZQLYHd7g0R3UcJ9-lg>

Suscríbite y aprende en mis grupos de correo y facebook:
Programación accesible:
Envía un correo de suscripción a la dirección:
programacionaccesible+subscribe@...
O participa en Programación accesible en Facebook.
<https://facebook.com/groups/235117436637120>

tiflotronica: Si te gusta la electricidad y los chips ¡Aprende y aporta
sobre este tema tan apasionante!
Envía un correo de suscripción a la dirección:
tiflotronica+subscribe@...
Si te gusta la producción o ejecución de instrumentos musicales, participa
en Músicos ciegos y de baja visión en facebook.
<https://facebook.com/groups/590594451020594>
También puedes hacer tus consultas sobre tu lector de pantallas favorito en
la comunidad de NVDA en español (facebook)
<https://facebook.com/groups/298402187029900>


El mié., 5 feb. 2020 a las 16:40, ChrisLM (<@Christianlm>) escribió:

Hi,

before open a issue, can someone else try to open the windows task
manager with control+shift+escape, or run taskmgr?

I have encountered serious problems in the task manager dialog using
last NVDA rc3, last alpha and running the source master...


cheers,



--
Chris.




Re: problems opening the task manager

Noelia Ruiz
 

Hi, me too. Maybe related to recent Java support?
This is listened and shown in speech viewer:
C:\Program Files\Java\jre1.8.0_211\bin\jabswitch.exe terminal
The Java Access Bridge has been

If you run source master, not an installed copy, though Java support
is not enabled from NVDA itself, maybe affected by a previous try if
you didn't restart the computer?
David is mentioning some previous issues, but I think this can be different.
Also, years ago NV Access worked on performance issues also related to
task viewer:

https://github.com/nvaccess/nvda/issues/5293
https://github.com/nvaccess/nvda/commit/020e3f63349357f06ac1bf7f1c62ac4dd66e99d1

Hope this helps


2020-02-05 23:40 GMT+01:00, ChrisLM <@Christianlm>:

Hi,

before open a issue, can someone else try to open the windows task
manager with control+shift+escape, or run taskmgr?

I have encountered serious  problems in the task manager dialog using
last NVDA rc3, last alpha and running the source master...


cheers,



--
Chris.




Re: problems opening the task manager

DaVid
 

You're talking about the slow response when opening the task manager?
Its a very known issue, but some people thought that is not relevant to solve. I installed the task manager of windows 7, where all the tings work properly.

Regards,
David CM
Ingeniero en computación (ITCR)
Experto certificado en NVDA.
correo: dhf360@...

Encuentra mis proyectos libres en github.
y las publicaciones en mi canal de youtube.

Suscríbite y aprende en mis grupos de correo y facebook:
Programación accesible:
Envía un correo de suscripción a la dirección: programacionaccesible+subscribe@...
O participa en Programación accesible en Facebook.

tiflotronica: Si te gusta la electricidad y los chips ¡Aprende y aporta sobre este tema tan apasionante!
Envía un correo de suscripción a la dirección: tiflotronica+subscribe@...
Si te gusta la producción o ejecución de instrumentos musicales, participa en Músicos ciegos y de baja visión en facebook.
También puedes hacer tus consultas sobre tu lector de pantallas favorito en la comunidad de NVDA en español (facebook)


El mié., 5 feb. 2020 a las 16:40, ChrisLM (<llajta2012@...>) escribió:
Hi,

before open a issue, can someone else try to open the windows task
manager with control+shift+escape, or run taskmgr?

I have encountered serious  problems in the task manager dialog using
last NVDA rc3, last alpha and running the source master...


cheers,



--
Chris.




problems opening the task manager

ChrisLM
 

Hi,

before open a issue, can someone else try to open the windows task manager with control+shift+escape, or run taskmgr?

I have encountered serious  problems in the task manager dialog using last NVDA rc3, last alpha and running the source master...


cheers,



--
Chris.

Re: NVDA crashes if non-ASCII characters are in the path

Nikita
 

Unfortunately, this is a rather serious problem, the danger of which is probably underestimated.
Because of this problem, it is impossible to run new NVDA if the path to unpacked version contains non-ASCII characters.
As a result, inexperienced users may not understand why the new NVDA portable does not start.
There are Non-ASCII characters in languages based on the Latin alphabet, for example, French, German, Spanish. The so-called diacritics.
It is also bad that the log of NVDA does not contain any errors. NVDA crashes before it has time to write something.
This is an old bug that manifested even in Python 2 versions. That is not a problem of Python 3 migration.

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Brian's Mail list account via Groups.Io
Sent: Wednesday, February 05, 2020 8:54 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] NVDA crashes if non-ASCII characters are in the path

I wonder how many people this might affect? If somebody likes espeak, one
supposes this will be people who use other languages than the Latin based
ones with this synth. I could not see the issue on the Espeak mail list, so
suspect its been around for a while. Could an older version be used to
temporarily fix this as it might make some people not want to switch,
assuming of course the problem is not already in the current stable python
2. I'd not know.

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: "Reef Turner" <reef@...>
To: <nvda-devel@groups.io>
Sent: Wednesday, February 05, 2020 9:10 AM
Subject: Re: [nvda-devel] NVDA crashes if non-ASCII characters are in the
path


Hi Nikita,

Thanks for pointing this out. It is a known issue [1]. We are confident this
is caused by an issue in espeak and there is little we can do about it in
the short term. We hope that the espeak maintainers will fix this issue, but
unfortunately it is too late for a fix to be included in 2019.3.

[1] https://github.com/nvaccess/nvda/issues/10607

Re: NVDA crashes if non-ASCII characters are in the path

Brian's Mail list account
 

I wonder how many people this might affect? If somebody likes espeak, one supposes this will be people who use other languages than the Latin based ones with this synth. I could not see the issue on the Espeak mail list, so suspect its been around for a while. Could an older version be used to temporarily fix this as it might make some people not want to switch, assuming of course the problem is not already in the current stable python 2. I'd not know.

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: "Reef Turner" <reef@...>
To: <nvda-devel@groups.io>
Sent: Wednesday, February 05, 2020 9:10 AM
Subject: Re: [nvda-devel] NVDA crashes if non-ASCII characters are in the path


Hi Nikita,

Thanks for pointing this out. It is a known issue [1]. We are confident this is caused by an issue in espeak and there is little we can do about it in the short term. We hope that the espeak maintainers will fix this issue, but unfortunately it is too late for a fix to be included in 2019.3.

[1] https://github.com/nvaccess/nvda/issues/10607

NVDA 2019.3rc3 now available for testing

Reef Turner
 

Hi all,

 

NVDA 2019.3rc3 has just been released for testing.

 

Changes from RC2:

 

• Updated translations for many languages

 

 

Full blog post: https://www.nvaccess.org/post/nvda-2019-3rc3-now-available-for-testing/

 

Reef Turner
Software Developer 

 

www.nvaccess.org

Facebook: https://www.facebook.com/NVAccess
Twitter: @NVAccess 

 

Re: NVDA crashes if non-ASCII characters are in the path

Reef Turner
 

Hi Nikita,

Thanks for pointing this out. It is a known issue [1]. We are confident this is caused by an issue in espeak and there is little we can do about it in the short term. We hope that the espeak maintainers will fix this issue, but unfortunately it is too late for a fix to be included in 2019.3.


[1] https://github.com/nvaccess/nvda/issues/10607

NVDA crashes if non-ASCII characters are in the path

Nikita
 

Hello everybody!

Now if the path to the nvda.exe contains non-ASCII characters, the NVDA will crash.

At a minimum, the problematic component is eSpeak. With some other synthesizers, NVDA may start.

However, I'm not sure that eSpeak is the only component experiencing such problems.

Tell me, please, is this a known problem?

If so, is it considered a bug that is planned to be fixed?

Regards, Nikita.

NVDA 2019.3 and add-ons: more add-ons buying compatibility ticket

 

Hi NVDA developers and add-ons community,

 

Since we had two betas in a span of days, I figured it is time to give you an update as to what’s going on with add-ons and their compatibility with 2019.3:

 

There’s nothing to report expect…

 

NVDA Remote add-on is getting closer to making itself NVDA 2019.3 ready. Python 3 compatibility code from NV Access was merged into NVDA Remote add-on repo with some work to be done. Thus the compatibility status for this add-on is now “work in progress”.

 

Hopefully the next briefing will be sent when 2019.3 release candidate (RC) is sent. At that point, the add-ons community should enter release preparation phase where authors should start publishing NVDA 2019.3 compatible versions of add-ons or announce when compatible versions will be released to stable channel (I myself will publish schedule for my add-ons within 24 hours after 2019.3 RC goes out).

 

Cheers,

Joseph

Strange issue with NVDA and queueHandler.eventQueue?

DaVid
 

Hi there.
Today my copy of NVDA was blocked. I was using chrome at the time.
When I read the log, the function that froze NVDA was "queue.empty()"
But "queue.empty" is used to check if the queue has pending tasks or not. So, this function shoulndn't block anything.
I was unable to restart NVDA. Then I slept my laptop and started it again, NVDA didn't respond but in this case I could restart NVDA.
This is the log:

WARNING - watchdog._watcher (18:10:17.574) - watchdog (3208):
Core frozen in stack:
  File "nvda.pyw", line 215, in <module>
  File "core.pyc", line 545, in main
  File "wx\core.pyc", line 2134, in MainLoop
  File "gui\__init__.pyc", line 1030, in Notify
  File "core.pyc", line 515, in run
  File "queueHandler.pyc", line 83, in pumpAll
  File "queueHandler.pyc", line 46, in flushQueue
  File "queue.pyc", line 107, in empty

Regards,
David CM
Ingeniero en computación (ITCR)
Experto certificado en NVDA.
correo: dhf360@...

Encuentra mis proyectos libres en github.
y las publicaciones en mi canal de youtube.

Suscríbite y aprende en mis grupos de correo y facebook:
Programación accesible:
Envía un correo de suscripción a la dirección: programacionaccesible+subscribe@...
O participa en Programación accesible en Facebook.

tiflotronica: Si te gusta la electricidad y los chips ¡Aprende y aporta sobre este tema tan apasionante!
Envía un correo de suscripción a la dirección: tiflotronica+subscribe@...
Si te gusta la producción o ejecución de instrumentos musicales, participa en Músicos ciegos y de baja visión en facebook.
También puedes hacer tus consultas sobre tu lector de pantallas favorito en la comunidad de NVDA en español (facebook)

Dual Voice add-on: is anyone willing to make it NVDA 2019.3 ready?

 

Hi all,

 

As noted in the following GitHub issue:

https://github.com/nvaccess/nvda/issues/10740

 

Dual Voice add-on isn’t NVDA 2019.3 ready, and attempts to contact the author isn’t working. So may I suggest someone taking a look at this add-on and see what can be done? The add-on can be found at:

https://addons.nvda-project.org/addons/dualvoice.en.html

 

Cheers,

Joseph

Re: [nvda] NVDA 2019.3 Beta 3 now available

Rui Fontes
 

Hello!


The problem is not how to know what character is...

The problem is that this NVDA version causes a serious problem and we are not yet absolutly sure which add-on is the culpry... and why...


For me, it is a show stopper problem...


Rui Fontes

NVDA portuguese team


Às 09:05 de 30/01/2020, hurrikennyandopo ... escreveu:

Hi


are you talking about the add on that after a second or 2 would say the letter  it was on like A  for alfa B for bravo etc.


I just can not think what that add on name was called.


are you aware also you can find out what the letter is on the numeric keypad if using the review cursor


Hitting the number 2 of the numeric keypad 2 times would say it like that or 5 on the numeric key pad would do the word if hit 3 times..


Gene nz


On 30/01/2020 9:47 pm, Ralf Kefferpuetz wrote:

Hi Quentin,

Reading by character stopped for me in this version as well as in any alpha version newer than 28th Jan.

 

Cheers,

Ralf

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen
Sent: Donnerstag, 30. Januar 2020 01:49
To: nvda@nvda.groups.io
Subject: [nvda] NVDA 2019.3 Beta 3 now available

 

Hi everyone,

 

As you are all quick off the mark, this isn't completely new news, but confirming that yes, NVDA 2019.3 beta 3 is now available from: https://www.nvaccess.org/post/nvda-2019-3beta3-now-available-for-testing/ 

 

This is slight progression from the previous beta so you shouldn't notice too many big changes - of course as always happens, as we move closer to the final release, we don't put as many big new features in, but rather try to ensure that everything is stable and fix bugs people have reported in previous betas.

 

If you do encounter any issues, please do report them: https://github.com/nvaccess/nvda/issues  If you could also clarify whether they are new issues or existing issues (which hadn't previously been reported) that would be really helpful - both are important to know about, but being able to pinpoint when something started being an issue helps narrow down where to look for a fix.

 

All things going well, this will be the last beta before the release candidate, which will be just before the final stable release.

 

Kind regards

 

Quentin.

 

--

Quentin Christensen
Training and Support Manager

 

Re: Object properties in speech functions

Reef Turner
 

I think this would be quite hard to achieve currently. Note that we have previously recommended this as a project for Google Summer of Code: https://github.com/nvaccess/nvda/wiki/GSOC-2019-Ideas-List#customize-order-and-inclusion-of-object-and-formatting-information-to-speech-and-braille.

My thoughts on a pathway towards this, is gradually convert all items in a speech sequence to some kind of speech command. Wrapping string items with a class that includes some metadata about it's origin. Eventually disallowing str objects in the speech sequence. Tagging speech that is essentially "NVDA UI" (eg "focus mode", or "selected" in "x selected"), as well tagging "name", "role", "value", "description" text could allow for some interesting innovation in how speech is presented.

I don't have a timeline on this. Note, this would be a compatibility breaking change.

Re: Object properties in speech functions

Alberto Buffolino
 

James Scholes, il 28/01/2020 21.31, ha scritto:
But the comment before the function in question seems to indicate that this part of the code is crying out for a refactor anyway:
Alberto:
true. As many other functions of speech module.
So... I'll see in future :)
Thanks James for replies.
Alberto

Re: Object properties in speech functions

James Scholes
 

Makes sense, and from a glance over the code, your assertion is correct. You would need to monkey-patch that function, presumably, to achieve what you're after. But the comment before the function in question seems to indicate that this part of the code is crying out for a refactor anyway:

# C901 'getPropertiesSpeech' is too complex
# Note: when working on getPropertiesSpeech, look for opportunities to simplify
# and move logic out into smaller helper functions.

Regards,

James Scholes

On 28/01/2020 at 2:21 pm, Alberto Buffolino wrote:
James Scholes, il 28/01/2020 21.01, ha scritto:
I'm not sure what you're asking.  Could you expand on your use case, and why you believe it is currently not feasible?
Alberto:
Hi James,
some users have asked me to provide a way to customize NVDA when it speaks objects, so to sort or hide some information. For example, to have "checked Save configuration on exit Checkbox", instead of "Save configuration on exit checkbox checked".
I was asking for a confirmation about my comprehension of object information processing. If it is as I think, I can do nothing with a add-on that simply changes order of information in properties/speechSequence before/after getPropertiesSpeech execution.
Ok, I'm not sure it's more clear now... 😅
Alberto

Re: Object properties in speech functions

Alberto Buffolino
 

James Scholes, il 28/01/2020 21.01, ha scritto:
I'm not sure what you're asking.  Could you expand on your use case, and why you believe it is currently not feasible?
Alberto:
Hi James,
some users have asked me to provide a way to customize NVDA when it speaks objects, so to sort or hide some information. For example, to have "checked Save configuration on exit Checkbox", instead of "Save configuration on exit checkbox checked".
I was asking for a confirmation about my comprehension of object information processing. If it is as I think, I can do nothing with a add-on that simply changes order of information in properties/speechSequence before/after getPropertiesSpeech execution.
Ok, I'm not sure it's more clear now... 😅
Alberto

Re: Object properties in speech functions

James Scholes
 

I'm not sure what you're asking. Could you expand on your use case, and why you believe it is currently not feasible?

Regards,

James Scholes

On 28/01/2020 at 12:43 pm, Alberto Buffolino wrote:
Hi all,
I'm investigating about NVDA verbosity/object information order, for a possible add-on or pr.
If I understand correctly, at this time the more important point concerns speech.getPropertiesSpeech, that provides the main speech sequence according to a passed dictionary of properties to process (name, role, etc). But, I suppose, there is no guarantee that properties passed will have a value in speech sequence, so no mapping property->value is possible (from an add-on perspective).
Right?
Thanks for replies.
Alberto