Date   

Re: 2022 RC, Outlook 2019 and NVDA-Search

Gene
 

It sounds to me, as I recall one of the messages, as though the setting to automatically turn browse mode on is not checked.  This means that when a web page loads or an e-mail opens, you are not automatically placed in Browse Mode, as you should be by default.
Check the following setting:
Open the Browse mode dialog, control NVDA b.
Tab to a check box that says Enable browse mode on page load.
If it isn't checked, check it with the space bar.
Then press enter. 
See if the problem is solved.

Gene

On 5/13/2022 5:54 AM, Quentin Christensen wrote:

Have you restarted the PC since updating to the RC?  Sometimes odd things happen in-between updating NVDA (or other software) and restarting.

On Fri, May 13, 2022 at 3:46 PM Yeti <jbslists@...> wrote:
Hi Gene and All,

> Did the command work before you reassigned it?


I assigned the additional CTRL+F months or years ago and it worked fine for me over many NVDA-Updates all the time.

Per Aspera

Yeti








--
Quentin Christensen
Training and Support Manager



Re: 2022 RC, Outlook 2019 and NVDA-Search

Quentin Christensen
 

Have you restarted the PC since updating to the RC?  Sometimes odd things happen in-between updating NVDA (or other software) and restarting.


On Fri, May 13, 2022 at 3:46 PM Yeti <jbslists@...> wrote:
Hi Gene and All,

> Did the command work before you reassigned it?


I assigned the additional CTRL+F months or years ago and it worked fine for me over many NVDA-Updates all the time.

Per Aspera

Yeti








--
Quentin Christensen
Training and Support Manager


Re: NVDA 2022.1 release candidate is now available

 

Hi,

A crash dump is generated if NVDA is told to generate it when it crashes (that's one way).

Based on the log attached to the GitHub issue, sounds like there is a miscommunication between a speech synthesizer driver and wxPython regarding app readiness. In other words, NVDA crashes because it or one of its components tried to do work that required presence of a specific data in memory.

Cheers,

Joseph


Re: NVDA 2022.1 release candidate is now available

Alexandre Alves Toco
 

I just opened the bug and the link is:

https://github.com/nvaccess/nvda/issues/13694#issue-1235034524


But there is no dump file.


Em 12/05/2022 23:33, sean@... escreveu:


Re: 2022 RC, Outlook 2019 and NVDA-Search

Yeti
 

Hello Luke and All,

That is the behavior you would get if you were in focus
mode,
not in browse mode. Are you sure you are
in browse mode?
Well, I think, this is an end where we can pull.
- I write this mail.
- Press CTRL+F
- the standard behavior of outlook happens
- I press NVDA+space, NVDA goes to browse mode
- making that sure by pressing "h", NVDA sais: no further
headline
- Press CTRL+F: NVDA search opens.
This is, what you expect to happen. Isn't it?

I can understand this somehow to be correct.

Anyway:
It was different with NVDA 21.3.x and earlier on all my
systems.
There NVDA search came up in focus mode by pressing CTRL+F
as well.

But if the behavior you describe is the right one, I will be
used to it in some days or weeks.

But, Hmhm - Isn't there a way to bring up NVDA search even
in focus mode?

Ad Astra

Yeti


Re: 2022 RC, Outlook 2019 and NVDA-Search

Luke Davis
 

Yeti wrote:

CTRL+F forwards the mail or opens the search and replace dialog of outlook (depending of reading or writing), as desired without NVDA
That is the behavior you would get if you were in focus mode, not in browse mode. Are you sure you are in browse mode?

Luke
"The first principle is that you must not fool yourself and you are the easiest person to fool." - Richard P. Feynman


how to fill out a PDF with NVDA

Bob Cavanaugh
 

Hi all,
Well, what do you know, I actually have a fillable PDF that I'm having
problems with. At least it's a fillable file, unlike most, where they
aren't even able to be filled even when they're asking for
information. Well, that's beside the point, the question is how do I
actually fill these out using Adobe Reader with NVDA? NVDA sees that
an edit box exists, but I can't tab between edit boxes like you would
on a webpage, and when I try to type into the edit box, even in focus
mode, nothing appears to be typed. What do I do?
Bob


Re: 2022 RC, Outlook 2019 and NVDA-Search

Yeti
 

Hi Gene and All,

Did the command work before you reassigned it?

I assigned the additional CTRL+F months or years ago and it worked fine for me over many NVDA-Updates all the time.

Per Aspera

Yeti


Re: 2022 RC, Outlook 2019 and NVDA-Search

Yeti
 

HI Luke and All,

Can you tell more about what you mean by it doesn't work?
What does it do or not do?
CTRL+F forwards the mail or opens the search and replace dialog of outlook (depending of reading or writing), as desired without NVDA

What does NVDA input help (NVDA+1) say about the key command?
Nothing but the pressed key.
Btw. This is the same with NVDA+CTRL+F

Have you checked in input gestures, to make sure it is still assigned?
Yes I did.
And I reassigned it in advance.

During reassigning I deleted

CTRL+F.

Doing this the standard assignment key

NVDA+CTRL+F

Disappeared as well.

So maybe there is something wrong with the command itself?

My system is German, so I ask my self, if this can be the result of an error in German localization?

Btw. Many other assigned NVDA hotkeys - such as NVDA
+1 or NVDA+n still work as usual 🙍‍♂️💦
1
Any other questions or ideas?

Per Aspera

Yeti


Re: 2022 RC, Outlook 2019 and NVDA-Search

Gene
 

Did the command work before you reassigned it?

Gene

On 5/12/2022 11:14 PM, Yeti wrote:
Additional info:
This is not a matter of the shortcut

CTRL+F

It does not work with the default key

NVDA+CTRL+F

as well

-----Ursprüngliche Nachricht-----
Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag
von Yeti
Gesendet: Freitag, 13. Mai 2022 06:07
An: nvda@nvda.groups.io
Betreff: [nvda] 2022 RC, Outlook 2019 and NVDA-Search

Hello Listers,

I've installed the 2022.1 RC yesterday and most Things work
fine.
But one thing is sad:

I assigned the Key

CTRL+F to the Command NVDA-Search

because I find this often more helpful, than the "normal"
search of many applications.

This Command with this hotkey works fine in FF and Notepad,
but not anymore in an open Mail in Outlook. Not in plane
text and not in HTML mails.
This was different in the last 2021.x

Thanks in advance

Yeti

System:
- Windows: Version10.0.19043 Build 19043
- Outlook 2019 2204 Build 16.0.15128.20210) 64 Bit













Re: 2022 RC, Outlook 2019 and NVDA-Search

Luke Davis
 

Yeti wrote:

I assigned the Key CTRL+F to the Command NVDA-Search [.]
This Command with this hotkey works fine in FF and Notepad, but not anymore in an open Mail in Outlook.
I do the same thing, and this is still working fine for me in Outlook 2019.

Can you tell more about what you mean by it doesn't work?

What does it do or not do?

What does NVDA input help (NVDA+1) say about the key command?

Have you checked in input gestures, to make sure it is still assigned?

--
Luke
"The first principle is that you must not fool yourself and you are the easiest person to fool." - Richard P. Feynman


Re: 2022 RC, Outlook 2019 and NVDA-Search

Yeti
 

Additional info:
This is not a matter of the shortcut

CTRL+F

It does not work with the default key

NVDA+CTRL+F

as well

-----Ursprüngliche Nachricht-----
Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag
von Yeti
Gesendet: Freitag, 13. Mai 2022 06:07
An: nvda@nvda.groups.io
Betreff: [nvda] 2022 RC, Outlook 2019 and NVDA-Search

Hello Listers,

I've installed the 2022.1 RC yesterday and most Things work
fine.
But one thing is sad:

I assigned the Key

CTRL+F to the Command NVDA-Search

because I find this often more helpful, than the "normal"
search of many applications.

This Command with this hotkey works fine in FF and Notepad,
but not anymore in an open Mail in Outlook. Not in plane
text and not in HTML mails.
This was different in the last 2021.x

Thanks in advance

Yeti

System:
- Windows: Version10.0.19043 Build 19043
- Outlook 2019 2204 Build 16.0.15128.20210) 64 Bit


2022 RC, Outlook 2019 and NVDA-Search

Yeti
 

Hello Listers,

I've installed the 2022.1 RC yesterday and most Things work
fine.
But one thing is sad:

I assigned the Key

CTRL+F to the Command NVDA-Search

because I find this often more helpful, than the "normal"
search of many applications.

This Command with this hotkey works fine in FF and Notepad,
but not anymore in an open Mail in Outlook. Not in plane
text and not in HTML mails.
This was different in the last 2021.x

Thanks in advance

Yeti

System:
- Windows: Version10.0.19043 Build 19043
- Outlook 2019 2204 Build 16.0.15128.20210) 64 Bit


Re: NVDA and reporting of spelling error

William
 

Quentin,

Thanks for creating this issue.



Quentin Christensen 於 13/5/2022 11:47 寫道:

As has been found, spelling errors are reported when moving by word / line, and also during say all, but not when moving by paragraph.  As as been suggested, there could be several reasons for this, none of which, I would think, are deliberate.  I have written up an issue for this at: https://github.com/nvaccess/nvda/issues/13693



On Fri, May 13, 2022 at 1:38 PM Luke Davis <luke@...> wrote:
Gene wrote:

> Errors are announced in read to end so it makes no logical sense for paragraph reading to be excluded.

I hadn't actually tested this when writing that, I sit corrected.

I did just play with it a little though.

Reading by paragraph is a Word function, not an NVDA function. NVDA is probably
getting a blob of text from Word in that case, without any of the normal
formatting indicators.

William, considering that sayall includes spelling errors--which I hadn't
realized--personally I think this is either a bug or an oversight, not an
intentional design choice.

If it is along the lines of what Rui said, it may be fixable. If it is closer to
what I suspect is happening, there is probably nothing that can be done about
it.

--
Luke
"The first principle is that you must not fool yourself and you are the easiest person to fool." - Richard P. Feynman







--
Quentin Christensen
Training and Support Manager


Re: NVDA and reporting of spelling error

Sarah k Alawami
 

Oh wow? I knew about browse mode, I use it, but not in winword. I’ll have to try that the next time.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Rui Fontes
Sent: Thursday, May 12, 2022 6:35 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA and reporting of spelling error

 

In the user guide...

 

NVDA+Space puts NVDA in browse mode...

In browse mode you can press w to move from error to error...

 

Rui Fontes

 

Às 02:31 de 13/05/2022, Sarah k Alawami escreveu:

I actually did not know this, where is this documented?

 

Take care to all.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of William
Sent: Thursday, May 12, 2022 5:10 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA and reporting of spelling error

 

> Did you know you can navigate between misspelled words by pressing NVDA plus Space, then W? When you find a misspelled word, press your applications key or Shift plus F10 to open the context menu, in order to correct the word. If you want to correct the word manually, you'll need to press NVDA plus Space again. I hope this is helpful.

 

Correct, but in reality, I cannot do any correction without first reading the whole sentence, cause sometimes the spelling errors suggested by word is not correct.

 

 

 

Abbie Taylor 13/5/2022 06:47 寫道:

I'm noticing the same thing. So, I'm assuming it's normal.

Did you know you can navigate between misspelled words by pressing NVDA plus Space, then W? When you find a misspelled word, press your applications key or Shift plus F10 to open the context menu, in order to correct the word. If you want to correct the word manually, you'll need to press NVDA plus Space again. I hope this is helpful.


Re: NVDA and reporting of spelling error

Quentin Christensen
 

As has been found, spelling errors are reported when moving by word / line, and also during say all, but not when moving by paragraph.  As as been suggested, there could be several reasons for this, none of which, I would think, are deliberate.  I have written up an issue for this at: https://github.com/nvaccess/nvda/issues/13693



On Fri, May 13, 2022 at 1:38 PM Luke Davis <luke@...> wrote:
Gene wrote:

> Errors are announced in read to end so it makes no logical sense for paragraph reading to be excluded.

I hadn't actually tested this when writing that, I sit corrected.

I did just play with it a little though.

Reading by paragraph is a Word function, not an NVDA function. NVDA is probably
getting a blob of text from Word in that case, without any of the normal
formatting indicators.

William, considering that sayall includes spelling errors--which I hadn't
realized--personally I think this is either a bug or an oversight, not an
intentional design choice.

If it is along the lines of what Rui said, it may be fixable. If it is closer to
what I suspect is happening, there is probably nothing that can be done about
it.

--
Luke
"The first principle is that you must not fool yourself and you are the easiest person to fool." - Richard P. Feynman







--
Quentin Christensen
Training and Support Manager


Re: NVDA and reporting of spelling error

Luke Davis
 

Gene wrote:

Errors are announced in read to end so it makes no logical sense for paragraph reading to be excluded.
I hadn't actually tested this when writing that, I sit corrected.

I did just play with it a little though.

Reading by paragraph is a Word function, not an NVDA function. NVDA is probably getting a blob of text from Word in that case, without any of the normal formatting indicators.

William, considering that sayall includes spelling errors--which I hadn't realized--personally I think this is either a bug or an oversight, not an intentional design choice.

If it is along the lines of what Rui said, it may be fixable. If it is closer to what I suspect is happening, there is probably nothing that can be done about it.

--
Luke
"The first principle is that you must not fool yourself and you are the easiest person to fool." - Richard P. Feynman


Re: NVDA and reporting of spelling error

Gene
 

I said it announces spelling errors when using read to end. 

Gene

On 5/12/2022 9:23 PM, William wrote:

Interestingly, if I press num pad + or nvda +down arrow to read to the end, it does report spelling errors.


Gene 於 13/5/2022 10:16 寫道:
Errors are announced in read to end so it makes no logical sense for paragraph reading to be excluded.  While I don't have a particular opinion about whether this matters to any extent, it is an interesting question as to why.

Gene

On 5/12/2022 9:08 PM, Luke Davis wrote:
When you're reading to hear the content, or reading for pleasure, do you really want to be hearing spelling errors?

I don't. I would rather hear them only when reading by word or line, because it is then that I am editing and not just reading.

I suspect something like that--the difference between reading for content and reading for editing--is why it works this way.

Luke








Re: NVDA 2022.1 release candidate is now available

Sean Budd (NV Access)
 


Re: NVDA and reporting of spelling error

William
 

Interestingly, if I press num pad + or nvda +down arrow to read to the end, it does report spelling errors.


Gene 於 13/5/2022 10:16 寫道:

Errors are announced in read to end so it makes no logical sense for paragraph reading to be excluded.  While I don't have a particular opinion about whether this matters to any extent, it is an interesting question as to why.

Gene

On 5/12/2022 9:08 PM, Luke Davis wrote:
When you're reading to hear the content, or reading for pleasure, do you really want to be hearing spelling errors?

I don't. I would rather hear them only when reading by word or line, because it is then that I am editing and not just reading.

I suspect something like that--the difference between reading for content and reading for editing--is why it works this way.

Luke






5921 - 5940 of 101039