Re: rate of speech
Mohamed
Yep, that's what I've been doing for about a year now, especially
since I like to play with synthesizers that can be unstable, not
saving configuration on exit means I don't have to worry about a
bad synth making NVDA unusable.
On 10/3/2018 3:21 PM, Gene wrote:
|
|
Re: NVDA and Win 10 1809
Robert Doc Wright godfearer
i am not running into tis problem.
toggle quoted messageShow quoted text
----- Original Message -----
From: "Don H" <lmddh50@...> To: <nvda@nvda.groups.io> Sent: Tuesday, October 2, 2018 6:36 PM Subject: [nvda] NVDA and Win 10 1809 NVDA seems to be running great with Win 10 1809. There is one strange thing that NVDA is voicing when entering the settings app. NVDA says
|
|
Re: FW: [win10] A small request: can folks using NVDA 2018.3.x on Windows 10 Version 1809 try running intensive tasks and see if File Explorer responds?
Robert Doc Wright godfearer
it works just fine. I'm having it max match my
X-men folder of movies. I opened another drive and I can move within it with no
problems. I was the one who was having the problem with having to wait until a
process had completed before I could do anything. thank you very
much!!!
|
|
Re: rate of speech
Gene
This appears to be one more example of why the
default setting that NVDA should save changes on exit is a really bad default
setting and should be changed. It would be a good idea for users to change
the setting and it shouldn't be the default NVDA setting.
One of the reasons Window-eyes users felt freer to
experiment than did JAWS users, at least thos who knew about this difference, is
that Window-eyes didn't save settings permanently unless you manually saved
them. That should be the same with NVDA. It's too easy to
accidentally or inadvertently save settings you don't intend to save if save on
exit is the default. there is such a thing as too much automation.
I'm quite sure, though I don't recall if I tested
this, that speech settings you change in this way wouldn't be saved if you had
save on exit disabled. Then you could close the program and revert to the
settings you were using before.
Also, with default settings set as they are now, as
long as you don't close the program, you can revert to the permanently saved
settings by using the command control NVDA key r. So in the current case,
if the program has not been closed, using this command will revert to the speech
settings before you changed them.
If you make changes you do want to save
permanently, you can save them with control NVDA key c. I would urge
anyone who wants to use or try different settings without risking saving
settings you don't want to save because theese are experimental or temporary use
settings, to turn save settings on exit off and to only save settings when
desired manually.
Gene
----- Original Message -----
Hold down the NVDA key + Control then use right and left arrows to select the speech option you wish to change, and then the up and down arrows to change the speed, tone or voice act. Remember to keep those two keys held down as you make your changes. These do not revert to earlier settings when NVDA is restarted. Nice feature for making changes on the fly. Rick -----Original Message----- From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Tyler Spivey Sent: Wednesday, October 3, 2018 2:44 PM To: nvda@nvda.groups.io Subject: Re: [nvda] rate of speech Press control+NVDA+v, then alt+r. That brings you to the rate slider, where you can use left/right to adjust it. On 10/3/2018 10:05 AM, Howard Traxler wrote: > On my notebook (IBM thinkpad t40) I can use the > NVDA+shift+control nd up or ddown to change speech rate. On my new > HP6300 desktop, that key command makes it go faster but not slower. I > made the mistake of thinking after it got fast it would go in a circle > and start slow again. Not happen. Got it too fast to understand. > Now I can't get it slower again. Tried using jaws but it makes me > start the computer and, of course, jaws is off and nvda is running very fast. > Well then, there is narrator, but I can't remember how to start narrator. > > Any suggestions? > Thanks. > Howard >
|
|
Re: Captchas Revisited
Mallard <mallard@...>
My heartfelt condolences... (smile).
toggle quoted messageShow quoted text
Il 03/10/2018 19:45, Ron Canazzi ha scritto:
Someone just reported on another list that Runalla is defunct.
|
|
Re: SystrayList add-on: version 3.x, Python 3, end of support for unsupported Windows releases
Gene
thanks for your answers.
Whenever it happens, I hope the next full version
is backwards compatible to avoid such problems.
Gene
----- Original Message -----
From: Joseph Lee
Sent: Wednesday, October 03, 2018 2:06 PM
Subject: Re: [nvda] SystrayList add-on: version 3.x, Python 3, end
of support for unsupported Windows releases Hi, For the foreseeable future, yes. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of
Gene
After the current transition, is it likely that compatible add-ons will continue to be compatible for future versions of Python 3?
Gene ----- Original Message ----- From: Joseph Lee Sent: Wednesday, October 03, 2018 1:37 PM Subject: Re: [nvda] SystrayList add-on: version 3.x, Python 3, end of support for unsupported Windows releases
Hi, Current release process for Python 3.x notes that each 3.x release receives support for five years. We’ll move along Python 3.x releases. As for what Python 4.0.0 will be like, as of 2018, the crystal ball isn’t even showing that version yet. As for what add-on authors will do, it is up to them to decide. What we the community can do is provide guidelines and recommendations, as well as coordinate our efforts. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of
Gene
What will happen when Python 3 reaches end of life? Is all this going to be gone through again when Python 4 becomes the supported version? How many add-on developers are going to be willing to go through this every ten years? Doesn't each version of Python have a life cycle of ten years?
This needs further clarification.
Gene ----- Original Message ----- From: Joseph Lee Sent: Wednesday, October 03, 2018 11:58 AM Subject: [nvda] SystrayList add-on: version 3.x, Python 3, end of support for unsupported Windows releases
Dear NVDA community,
A few days ago the add-ons community were told the following:
SystrayList add-on 3.0 will make the code compatible with Python 3 and make it work with old Windows releases.
Subsequent comments indicate that, although we still need to support old Windows releases if given a chance, we should eventually move onto newer releases. Thus, the following will happen in November 2018 and beyond:
You don’t really have to use this add-on to access Taskbar and notification area – you can press Windows+T to move to Taskbar and Windows+B to move focus to notification area. The add-on is there for convenience.
As for the question of Python 3 and old Windows releases: the version of Python 3 NV Access and some developers are looking at does not support Windows releases earlier than 7. There is a version of Python 3 (version 3.4) that does support old Windows releases, but by the time NVDA moves to Python 3, that Python version will reach end of life (released in 2014, Python 3.4’s scheduled end of life is 2019). Coupled with the fact that recent NVDA requires Windows 7, it was decided to end support for old Windows releases from SystrayList add-on once we move to Python 3.
This naturally raises the question: if Python 3 drops support for Windows XP and Vista, and if one add-on drops support for these, how about other add-ons? Yes, other add-ons that exclusively rely on Python 2 will not work in Python 3 version of NVDA. There are some add-ons the community has come to rely on that assumes Python 2 from the outset, and for some, it is difficult to port the source code to Python 3 without extensive testing and modifications. This is especially true for speech synthesizer and braille display driver add-ons, as the way Python interprets texts has changed fundamentally in Python 3. This also means once we do use Python 3 in NVDA Core itself, we must say goodbye to Windows XP and Vista.
So what should the add-ons community do, and in extension, what can the global NVDA community do? Although the details of the transition is still being worked out (with some developers researching possible showstoppers), I recommend the following to be done for now until NV Access announces transition to Python 3:
For users of add-ons I created or am maintaining (SystrayList add-on included), I’ll make sure my add-ons are compatible with Python 3 the first day Python 3 edition of NVDA is released. Speaking of that progress, version 18.10 of Object Location Tones and ObjPad are Python 3 compatible, and in November, SystrayList 3.0.
Thanks. Cheers, Joseph
|
|
Re: rate of speech
ely.r@...
Afternoon,
toggle quoted messageShow quoted text
Hold down the NVDA key + Control then use right and left arrows to select the speech option you wish to change, and then the up and down arrows to change the speed, tone or voice act. Remember to keep those two keys held down as you make your changes. These do not revert to earlier settings when NVDA is restarted. Nice feature for making changes on the fly. Rick
-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Tyler Spivey Sent: Wednesday, October 3, 2018 2:44 PM To: nvda@nvda.groups.io Subject: Re: [nvda] rate of speech Press control+NVDA+v, then alt+r. That brings you to the rate slider, where you can use left/right to adjust it. On 10/3/2018 10:05 AM, Howard Traxler wrote: On my notebook (IBM thinkpad t40) I can use the
|
|
Re: SystrayList add-on: version 3.x, Python 3, end of support for unsupported Windows releases
Hi, For the foreseeable future, yes. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: Wednesday, October 3, 2018 12:05 PM To: nvda@nvda.groups.io Subject: Re: [nvda] SystrayList add-on: version 3.x, Python 3, end of support for unsupported Windows releases
After the current transition, is it likely that compatible add-ons will continue to be compatible for future versions of Python 3?
Gene ----- Original Message ----- From: Joseph Lee Sent: Wednesday, October 03, 2018 1:37 PM Subject: Re: [nvda] SystrayList add-on: version 3.x, Python 3, end of support for unsupported Windows releases
Hi, Current release process for Python 3.x notes that each 3.x release receives support for five years. We’ll move along Python 3.x releases. As for what Python 4.0.0 will be like, as of 2018, the crystal ball isn’t even showing that version yet. As for what add-on authors will do, it is up to them to decide. What we the community can do is provide guidelines and recommendations, as well as coordinate our efforts. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
What will happen when Python 3 reaches end of life? Is all this going to be gone through again when Python 4 becomes the supported version? How many add-on developers are going to be willing to go through this every ten years? Doesn't each version of Python have a life cycle of ten years?
This needs further clarification.
Gene ----- Original Message ----- From: Joseph Lee Sent: Wednesday, October 03, 2018 11:58 AM Subject: [nvda] SystrayList add-on: version 3.x, Python 3, end of support for unsupported Windows releases
Dear NVDA community,
A few days ago the add-ons community were told the following:
SystrayList add-on 3.0 will make the code compatible with Python 3 and make it work with old Windows releases.
Subsequent comments indicate that, although we still need to support old Windows releases if given a chance, we should eventually move onto newer releases. Thus, the following will happen in November 2018 and beyond:
You don’t really have to use this add-on to access Taskbar and notification area – you can press Windows+T to move to Taskbar and Windows+B to move focus to notification area. The add-on is there for convenience.
As for the question of Python 3 and old Windows releases: the version of Python 3 NV Access and some developers are looking at does not support Windows releases earlier than 7. There is a version of Python 3 (version 3.4) that does support old Windows releases, but by the time NVDA moves to Python 3, that Python version will reach end of life (released in 2014, Python 3.4’s scheduled end of life is 2019). Coupled with the fact that recent NVDA requires Windows 7, it was decided to end support for old Windows releases from SystrayList add-on once we move to Python 3.
This naturally raises the question: if Python 3 drops support for Windows XP and Vista, and if one add-on drops support for these, how about other add-ons? Yes, other add-ons that exclusively rely on Python 2 will not work in Python 3 version of NVDA. There are some add-ons the community has come to rely on that assumes Python 2 from the outset, and for some, it is difficult to port the source code to Python 3 without extensive testing and modifications. This is especially true for speech synthesizer and braille display driver add-ons, as the way Python interprets texts has changed fundamentally in Python 3. This also means once we do use Python 3 in NVDA Core itself, we must say goodbye to Windows XP and Vista.
So what should the add-ons community do, and in extension, what can the global NVDA community do? Although the details of the transition is still being worked out (with some developers researching possible showstoppers), I recommend the following to be done for now until NV Access announces transition to Python 3:
For users of add-ons I created or am maintaining (SystrayList add-on included), I’ll make sure my add-ons are compatible with Python 3 the first day Python 3 edition of NVDA is released. Speaking of that progress, version 18.10 of Object Location Tones and ObjPad are Python 3 compatible, and in November, SystrayList 3.0.
Thanks. Cheers, Joseph
|
|
Re: SystrayList add-on: version 3.x, Python 3, end of support for unsupported Windows releases
Gene
After the current transition, is it likely that
compatible add-ons will continue to be compatible for future versions of Python
3?
Gene
----- Original Message -----
From: Joseph Lee
Sent: Wednesday, October 03, 2018 1:37 PM
Subject: Re: [nvda] SystrayList add-on: version 3.x, Python 3, end
of support for unsupported Windows releases Hi, Current release process for Python 3.x notes that each 3.x release receives support for five years. We’ll move along Python 3.x releases. As for what Python 4.0.0 will be like, as of 2018, the crystal ball isn’t even showing that version yet. As for what add-on authors will do, it is up to them to decide. What we the community can do is provide guidelines and recommendations, as well as coordinate our efforts. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io>
On Behalf Of Gene
What will happen when Python 3 reaches end of life? Is all this going to be gone through again when Python 4 becomes the supported version? How many add-on developers are going to be willing to go through this every ten years? Doesn't each version of Python have a life cycle of ten years?
This needs further clarification.
Gene ----- Original Message ----- From: Joseph Lee Sent: Wednesday, October 03, 2018 11:58 AM Subject: [nvda] SystrayList add-on: version 3.x, Python 3, end of support for unsupported Windows releases
Dear NVDA community,
A few days ago the add-ons community were told the following:
SystrayList add-on 3.0 will make the code compatible with Python 3 and make it work with old Windows releases.
Subsequent comments indicate that, although we still need to support old Windows releases if given a chance, we should eventually move onto newer releases. Thus, the following will happen in November 2018 and beyond:
You don’t really have to use this add-on to access Taskbar and notification area – you can press Windows+T to move to Taskbar and Windows+B to move focus to notification area. The add-on is there for convenience.
As for the question of Python 3 and old Windows releases: the version of Python 3 NV Access and some developers are looking at does not support Windows releases earlier than 7. There is a version of Python 3 (version 3.4) that does support old Windows releases, but by the time NVDA moves to Python 3, that Python version will reach end of life (released in 2014, Python 3.4’s scheduled end of life is 2019). Coupled with the fact that recent NVDA requires Windows 7, it was decided to end support for old Windows releases from SystrayList add-on once we move to Python 3.
This naturally raises the question: if Python 3 drops support for Windows XP and Vista, and if one add-on drops support for these, how about other add-ons? Yes, other add-ons that exclusively rely on Python 2 will not work in Python 3 version of NVDA. There are some add-ons the community has come to rely on that assumes Python 2 from the outset, and for some, it is difficult to port the source code to Python 3 without extensive testing and modifications. This is especially true for speech synthesizer and braille display driver add-ons, as the way Python interprets texts has changed fundamentally in Python 3. This also means once we do use Python 3 in NVDA Core itself, we must say goodbye to Windows XP and Vista.
So what should the add-ons community do, and in extension, what can the global NVDA community do? Although the details of the transition is still being worked out (with some developers researching possible showstoppers), I recommend the following to be done for now until NV Access announces transition to Python 3:
For users of add-ons I created or am maintaining (SystrayList add-on included), I’ll make sure my add-ons are compatible with Python 3 the first day Python 3 edition of NVDA is released. Speaking of that progress, version 18.10 of Object Location Tones and ObjPad are Python 3 compatible, and in November, SystrayList 3.0.
Thanks. Cheers, Joseph
|
|
Re: NVDA not reading slides in Presentation mode "slide show complete"
Joshua Crary <JCrary@...>
Ive tried using arrow keys, using control plus A to high light, nothing is read ut loud.
toggle quoted messageShow quoted text
-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Mike Sedmak Sent: Wednesday, October 3, 2018 2:44 PM To: nvda@nvda.groups.io Subject: Re: [nvda] NVDA not reading slides in Presentation mode "slide show complete" Once the slideshow starts are you using the arrow keys to attempt to read the slides? On 10/3/18, Joshua Crary <JCrary@...> wrote: It is 7 slides and I start the slide show with F5, having had high Caution: This email originated from outside of Roxbury Community College. Do not click links or open attachments unless you recognize the sender and know the content is safe.
|
|
Re: rate of speech
Tyler Spivey
Press control+NVDA+v, then alt+r. That brings you to the rate slider,
toggle quoted messageShow quoted text
where you can use left/right to adjust it.
On 10/3/2018 10:05 AM, Howard Traxler wrote:
On my notebook (IBM thinkpad t40) I can use the
|
|
Re: NVDA not reading slides in Presentation mode "slide show complete"
Mike Sedmak
Once the slideshow starts are you using the arrow keys to attempt to
toggle quoted messageShow quoted text
read the slides?
On 10/3/18, Joshua Crary <JCrary@...> wrote:
It is 7 slides and I start the slide show with F5, having had high lighted
|
|
Re: SystrayList add-on: version 3.x, Python 3, end of support for unsupported Windows releases
Hi, Current release process for Python 3.x notes that each 3.x release receives support for five years. We’ll move along Python 3.x releases. As for what Python 4.0.0 will be like, as of 2018, the crystal ball isn’t even showing that version yet. As for what add-on authors will do, it is up to them to decide. What we the community can do is provide guidelines and recommendations, as well as coordinate our efforts. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: Wednesday, October 3, 2018 11:13 AM To: nvda@nvda.groups.io Subject: Re: [nvda] SystrayList add-on: version 3.x, Python 3, end of support for unsupported Windows releases
What will happen when Python 3 reaches end of life? Is all this going to be gone through again when Python 4 becomes the supported version? How many add-on developers are going to be willing to go through this every ten years? Doesn't each version of Python have a life cycle of ten years?
This needs further clarification.
Gene ----- Original Message ----- From: Joseph Lee Sent: Wednesday, October 03, 2018 11:58 AM Subject: [nvda] SystrayList add-on: version 3.x, Python 3, end of support for unsupported Windows releases
Dear NVDA community,
A few days ago the add-ons community were told the following:
SystrayList add-on 3.0 will make the code compatible with Python 3 and make it work with old Windows releases.
Subsequent comments indicate that, although we still need to support old Windows releases if given a chance, we should eventually move onto newer releases. Thus, the following will happen in November 2018 and beyond:
You don’t really have to use this add-on to access Taskbar and notification area – you can press Windows+T to move to Taskbar and Windows+B to move focus to notification area. The add-on is there for convenience.
As for the question of Python 3 and old Windows releases: the version of Python 3 NV Access and some developers are looking at does not support Windows releases earlier than 7. There is a version of Python 3 (version 3.4) that does support old Windows releases, but by the time NVDA moves to Python 3, that Python version will reach end of life (released in 2014, Python 3.4’s scheduled end of life is 2019). Coupled with the fact that recent NVDA requires Windows 7, it was decided to end support for old Windows releases from SystrayList add-on once we move to Python 3.
This naturally raises the question: if Python 3 drops support for Windows XP and Vista, and if one add-on drops support for these, how about other add-ons? Yes, other add-ons that exclusively rely on Python 2 will not work in Python 3 version of NVDA. There are some add-ons the community has come to rely on that assumes Python 2 from the outset, and for some, it is difficult to port the source code to Python 3 without extensive testing and modifications. This is especially true for speech synthesizer and braille display driver add-ons, as the way Python interprets texts has changed fundamentally in Python 3. This also means once we do use Python 3 in NVDA Core itself, we must say goodbye to Windows XP and Vista.
So what should the add-ons community do, and in extension, what can the global NVDA community do? Although the details of the transition is still being worked out (with some developers researching possible showstoppers), I recommend the following to be done for now until NV Access announces transition to Python 3:
For users of add-ons I created or am maintaining (SystrayList add-on included), I’ll make sure my add-ons are compatible with Python 3 the first day Python 3 edition of NVDA is released. Speaking of that progress, version 18.10 of Object Location Tones and ObjPad are Python 3 compatible, and in November, SystrayList 3.0.
Thanks. Cheers, Joseph
|
|
Re: NVDA not reading slides in Presentation mode "slide show complete"
Joshua Crary <JCrary@...>
It is 7 slides and I start the slide show with F5, having had high lighted the first slide.
toggle quoted messageShow quoted text
-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Mike Sedmak Sent: Wednesday, October 3, 2018 12:53 PM To: nvda@nvda.groups.io Subject: Re: [nvda] NVDA not reading slides in Presentation mode "slide show complete" A couple sanity check questions: How many slides in the presentation? Are you using f5 to start the presentation at the beginning? In the past I have found that if I use f5 then escape then f5 a second time, the slides are readable on the second time. YMMV Mike On 10/3/18, Joshua Crary <JCrary@...> wrote: Anyone have any input on this? I have a presentation on Friday and Caution: This email originated from outside of Roxbury Community College. Do not click links or open attachments unless you recognize the sender and know the content is safe.
|
|
Re: SystrayList add-on: version 3.x, Python 3, end of support for unsupported Windows releases
Gene
What will happen when Python 3 reaches end of
life? Is all this going to be gone through again when Python 4 becomes the
supported version? How many add-on developers are going to be willing to
go through this every ten years? Doesn't each version of Python have a
life cycle of ten years?
This needs further clarification.
Gene
----- Original Message -----
From: Joseph Lee
Sent: Wednesday, October 03, 2018 11:58 AM
Subject: [nvda] SystrayList add-on: version 3.x, Python 3, end of
support for unsupported Windows releases Dear NVDA community,
A few days ago the add-ons community were told the following:
SystrayList add-on 3.0 will make the code compatible with Python 3 and make it work with old Windows releases.
Subsequent comments indicate that, although we still need to support old Windows releases if given a chance, we should eventually move onto newer releases. Thus, the following will happen in November 2018 and beyond:
You don’t really have to use this add-on to access Taskbar and notification area – you can press Windows+T to move to Taskbar and Windows+B to move focus to notification area. The add-on is there for convenience.
As for the question of Python 3 and old Windows releases: the version of Python 3 NV Access and some developers are looking at does not support Windows releases earlier than 7. There is a version of Python 3 (version 3.4) that does support old Windows releases, but by the time NVDA moves to Python 3, that Python version will reach end of life (released in 2014, Python 3.4’s scheduled end of life is 2019). Coupled with the fact that recent NVDA requires Windows 7, it was decided to end support for old Windows releases from SystrayList add-on once we move to Python 3.
This naturally raises the question: if Python 3 drops support for Windows XP and Vista, and if one add-on drops support for these, how about other add-ons? Yes, other add-ons that exclusively rely on Python 2 will not work in Python 3 version of NVDA. There are some add-ons the community has come to rely on that assumes Python 2 from the outset, and for some, it is difficult to port the source code to Python 3 without extensive testing and modifications. This is especially true for speech synthesizer and braille display driver add-ons, as the way Python interprets texts has changed fundamentally in Python 3. This also means once we do use Python 3 in NVDA Core itself, we must say goodbye to Windows XP and Vista.
So what should the add-ons community do, and in extension, what can the global NVDA community do? Although the details of the transition is still being worked out (with some developers researching possible showstoppers), I recommend the following to be done for now until NV Access announces transition to Python 3:
For users of add-ons I created or am maintaining (SystrayList add-on included), I’ll make sure my add-ons are compatible with Python 3 the first day Python 3 edition of NVDA is released. Speaking of that progress, version 18.10 of Object Location Tones and ObjPad are Python 3 compatible, and in November, SystrayList 3.0.
Thanks. Cheers, Joseph
|
|
Problem with Adobe reader
Hi!
I have problem with adobe reader. It doesn't read a tables to me. It is maybe, because Adobe was updated. Have You somebody previous versions? Thank You. Marco
|
|
Re: Captchas Revisited
Ron Canazzi
Someone just reported on another list that Runalla is defunct.
toggle quoted messageShow quoted text
On 10/3/2018 12:56 PM, Sarah k Alawami wrote:
Rumolla if you can get it to workis grate.It is I think $1 for 100 credits and you have 3 months to use them but the service is grate. --
They Ask Me If I'm Happy; I say Yes. They ask: "How Happy are You?" I Say: "I'm as happy as a stow away chimpanzee on a banana boat!"
|
|
Re: FW: [win10] A small request: can folks using NVDA 2018.3.x on Windows 10 Version 1809 try running intensive tasks and see if File Explorer responds?
Hi,
toggle quoted messageShow quoted text
Yep, thanks for this one. This is going to be used to compare against those running 2018.3.x. Cheers, Joseph
-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Rui Fontes Sent: Wednesday, October 3, 2018 10:14 AM To: nvda@nvda.groups.io Subject: Re: [nvda] FW: [win10] A small request: can folks using NVDA 2018.3.x on Windows 10 Version 1809 try running intensive tasks and see if File Explorer responds? Running the latest version of Windows 10, 1809 Rel 17673, and last NVDA alpha, the lag in File explorer seems a thing of past... Rui Fontes Às 17:18 de 03/10/2018, Joseph Lee escreveu: Hi,study. Thanks. moment).
|
|
Re: FW: [win10] A small request: can folks using NVDA 2018.3.x on Windows 10 Version 1809 try running intensive tasks and see if File Explorer responds?
Rui Fontes
Running the latest version of Windows 10, 1809 Rel 17673, and last NVDA alpha, the lag in File explorer seems a thing of past...
toggle quoted messageShow quoted text
Rui Fontes Às 17:18 de 03/10/2018, Joseph Lee escreveu:
Hi,
|
|
Re: Files not showing
JM Casey <crystallogic@...>
*grins* It happens. Glad you found your files.
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Howard Traxler
Sent: October 3, 2018 12:55 PM To: nvda@nvda.groups.io Subject: Re: [nvda] Files not showing
How to be stupid:
Of course, I wouldn't make a mistake and put all my files into one of those subfolders? hahaha! So, when I looked into those subfolders, there they were.
See my next message for the next stupid mistake.
Thanks to all who tried to help. Howard
|
|