Can NVDA be placed in a default directory when creating a portable version?


Rowen Cary
 

Many people who create a portable version of NVDA for the first time think that they have placed the files in a unified directory, but this is not the case. They will find that the newly created NVDA contains multiple files, which are scattered in a folder. this is bad.


Gene
 

I wouldn’t object to a default folder being offered if none is specified by the user.  And if one is specified, a subfolder should be created in that folder containing the files.  As things stand now, when a portable copy is made, if a folder is specified, the files are placed in that folder and if there are other files, the NVDA files are mixed with the other files.  No warning is given at any time in the creation dialog about this.  This is a longstanding problem and it is important that the behavior be changed.  I would think this would be a very easy change and it should be done either in the current version or in the next production version, if not in the betas.
 
Gene

-----Original Message-----
From: Rowen Cary
Sent: Wednesday, November 10, 2021 7:32 PM
Subject: [nvda] Can NVDA be placed in a default directory when creating a portable version?
 

Many people who create a portable version of NVDA for the first time think that they have placed the files in a unified directory, but this is not the case. They will find that the newly created NVDA contains multiple files, which are scattered in a folder. this is bad.


Quentin Christensen
 

There is an open issue for this here: https://github.com/nvaccess/nvda/issues/3113

Don't forget to make sure any ideas for implementation are captured on the issue - as and when someone works on a fix, they will check the comments on the issue, not necessarily in here.

Kind regards

Quentin.

On Thu, Nov 11, 2021 at 12:54 PM Gene <gsasner@...> wrote:
I wouldn’t object to a default folder being offered if none is specified by the user.  And if one is specified, a subfolder should be created in that folder containing the files.  As things stand now, when a portable copy is made, if a folder is specified, the files are placed in that folder and if there are other files, the NVDA files are mixed with the other files.  No warning is given at any time in the creation dialog about this.  This is a longstanding problem and it is important that the behavior be changed.  I would think this would be a very easy change and it should be done either in the current version or in the next production version, if not in the betas.
 
Gene
-----Original Message-----
From: Rowen Cary
Sent: Wednesday, November 10, 2021 7:32 PM
Subject: [nvda] Can NVDA be placed in a default directory when creating a portable version?
 

Many people who create a portable version of NVDA for the first time think that they have placed the files in a unified directory, but this is not the case. They will find that the newly created NVDA contains multiple files, which are scattered in a folder. this is bad.



--
Quentin Christensen
Training and Support Manager


Gene
 

Its been opened since 2013.  I’m not hopeful.
 
Gene

-----Original Message-----
Sent: Wednesday, November 10, 2021 8:02 PM
Subject: Re: [nvda] Can NVDA be placed in a default directory when creating a portable version?
 
There is an open issue for this here: https://github.com/nvaccess/nvda/issues/3113
 
Don't forget to make sure any ideas for implementation are captured on the issue - as and when someone works on a fix, they will check the comments on the issue, not necessarily in here.
 
Kind regards
 
Quentin.
 
On Thu, Nov 11, 2021 at 12:54 PM Gene <gsasner@...> wrote:
I wouldn’t object to a default folder being offered if none is specified by the user.  And if one is specified, a subfolder should be created in that folder containing the files.  As things stand now, when a portable copy is made, if a folder is specified, the files are placed in that folder and if there are other files, the NVDA files are mixed with the other files.  No warning is given at any time in the creation dialog about this.  This is a longstanding problem and it is important that the behavior be changed.  I would think this would be a very easy change and it should be done either in the current version or in the next production version, if not in the betas.
 
Gene
-----Original Message-----
From: Rowen Cary
Sent: Wednesday, November 10, 2021 7:32 PM
Subject: [nvda] Can NVDA be placed in a default directory when creating a portable version?
 

Many people who create a portable version of NVDA for the first time think that they have placed the files in a unified directory, but this is not the case. They will find that the newly created NVDA contains multiple files, which are scattered in a folder. this is bad.

 
 
--
Quentin Christensen
Training and Support Manager


Rowen Cary
 

@Qchristensen's idea is very good, I am very happy to see the implementation of this pr. Another thing that is often talked about is that it is allowed to delete the configuration when uninstalling NVDA. I think this priority may be higher.


Quentin Christensen
 

Rowen, without drifting this conversation off topic, yes, there is an issue for removing the config when uninstalling as well.

Quentin.

On Thu, Nov 11, 2021 at 2:40 PM Rowen Cary <manchen_0528@...> wrote:

@Qchristensen's idea is very good, I am very happy to see the implementation of this pr. Another thing that is often talked about is that it is allowed to delete the configuration when uninstalling NVDA. I think this priority may be higher.



--
Quentin Christensen
Training and Support Manager


Sarah k Alawami
 

Actually for me when I create a portable copy in a folder  I believe it is all unified.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Rowen Cary
Sent: Wednesday, November 10, 2021 5:32 PM
To: nvda@nvda.groups.io
Subject: [nvda] Can NVDA be placed in a default directory when creating a portable version?

 

Many people who create a portable version of NVDA for the first time think that they have placed the files in a unified directory, but this is not the case. They will find that the newly created NVDA contains multiple files, which are scattered in a folder. this is bad.


 

On Thu, Nov 11, 2021 at 12:51 PM, Sarah k Alawami wrote:
Actually for me when I create a portable copy in a folder 

Key words here:  "in a folder"

If you designate a folder all of the portable NVDA content uses that folder as its "root folder" and gets created under it.

The problem here seems to be that many (and I hasten to add this is not saying they're wrong) are unaccustomed to actually specifying a folder in which to place something and that when you pick just a drive, it's going to use the root folder of that drive as its starting point.  Thus, if you already have files and folders at the root level of the drive you're using, the NVDA portable copy has its files at the root level and the folders it creates there as well.

To me, there is no "right way" for NVDA to do this, as many are accustomed to the idea that they must specify a folder on a drive, and if they don't, the root folder of the drive will be used, and very often that's precisely what's wanted so that you don't have to "drill down" in the folder structure of that drive to fire up your portable copy.

If NVDA were to create a subfolder then users would have to know what that subfolder was named (NVDA being the obvious choice).  But they'd then have to navigate to that folder to fire up NVDA portable.

I'm agnostic about whether or not a dedicated folder were created, because either choice has a class of users it's going to give consternation to.

One of the first things I try to teach my clients, and my partner (who seems to be a lost cause on this), is that you never "just allow" whatever it is to choose its own location.  You take the time to browse so that, even if you elect to use whatever location it is that's chosen as the default, you are aware of exactly where that thing is going to be created or saved.  Very often, it's not where you'd think, and then you have control over where it gets put.

When I go to create a portable copy from an already installed instance of NVDA, the first thing it asks is for you to specify the path, whether by typing it out or browsing (which is what I always do), and then checking which of the other two option checkboxes you may wish before hitting the Continue button.  Right there you have the power to choose precisely where you wish to have the portable copy created.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy

 


Sarah k Alawami
 

Right, it's a catch 22. I hav ealways made it a habit to choose a folder with anything, not sure if it was my computer teacher who drilled it into me or all the years I've pulled out all of my hair, lol!


Sarah Alawami, owner of TFFP. .

For more info go to our website. . to subscribe to the feed click here

Our discord is where you will know when we go live on youtube, twitch and odysee. Thanks Restream staff.

Videos of some of our podcasts can be found on odysee

You can support the podcast by subscribing via the tip jar. You will get early access episodes plus no adds. If you cannot do that, then leave a 5 star rating on our podcast using your podcast directory's rating system.

On 11 Nov 2021, at 10:12, Brian Vogel wrote:

On Thu, Nov 11, 2021 at 12:51 PM, Sarah k Alawami wrote:
Actually for me when I create a portable copy in a folder 

Key words here:  "in a folder"

If you designate a folder all of the portable NVDA content uses that folder as its "root folder" and gets created under it.

The problem here seems to be that many (and I hasten to add this is not saying they're wrong) are unaccustomed to actually specifying a folder in which to place something and that when you pick just a drive, it's going to use the root folder of that drive as its starting point.  Thus, if you already have files and folders at the root level of the drive you're using, the NVDA portable copy has its files at the root level and the folders it creates there as well.

To me, there is no "right way" for NVDA to do this, as many are accustomed to the idea that they must specify a folder on a drive, and if they don't, the root folder of the drive will be used, and very often that's precisely what's wanted so that you don't have to "drill down" in the folder structure of that drive to fire up your portable copy.

If NVDA were to create a subfolder then users would have to know what that subfolder was named (NVDA being the obvious choice).  But they'd then have to navigate to that folder to fire up NVDA portable.

I'm agnostic about whether or not a dedicated folder were created, because either choice has a class of users it's going to give consternation to.

One of the first things I try to teach my clients, and my partner (who seems to be a lost cause on this), is that you never "just allow" whatever it is to choose its own location.  You take the time to browse so that, even if you elect to use whatever location it is that's chosen as the default, you are aware of exactly where that thing is going to be created or saved.  Very often, it's not where you'd think, and then you have control over where it gets put.

When I go to create a portable copy from an already installed instance of NVDA, the first thing it asks is for you to specify the path, whether by typing it out or browsing (which is what I always do), and then checking which of the other two option checkboxes you may wish before hitting the Continue button.  Right there you have the power to choose precisely where you wish to have the portable copy created.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy