Re: [Nvda-dev] [NVDA] #405: NVDA doesn't use default config for installer

[NVDA T. <tr...@nv...>]

#405: NVDA doesn't use default config for installer
-------------------------+--------------------------------------------------
  Reporter:  criticview  |       Owner:                
      Type:  defect      |      Status:  reopened      
  Priority:  minor       |   Milestone:  2009.1        
 Component:  Installer   |     Version:  trunk         
Resolution:              |    Keywords:  default config
        Os:              |   Blockedby:                
  Blocking:              |  
-------------------------+--------------------------------------------------

Comment(by criticview):

 Replying to [comment:5 pvagner]:
 > Guys don't you think this is a regression?
 > Actually ability to reuse the existing config file whenever it's
 available was a feature not a bug.
 OK, but what do you do when you mess the config up? What if your config
 was specified to be ideal for another language than the one the installer
 will use.
 > NVDA has ability to recover the broken config file or fall to default
 setting when config file is not readable for some reason.
 >
 > I think we do need to rethink this scenario.
 If you install other products, say "jfw" for instance, the installation
 program doesn't use the customised config. Only after installation is
 complete, the custom settings are used.
 Maybe the installer could be in default config, but can ask to import
 previous settings (so that nvda uninstall is as clean as possible). If the
 config file can't be read, just ignore the question ...

-- 
Ticket URL: <http://www.nvda-project.org/ticket/405#comment:6>
NVDA <http://www.nvda-project.org/>
A free and open-source screen reader for Windows