Remember last setting

[GoogleCodeExporter]

#Is this a feature request? If so, describe your feature here:

It will be very convenient if waitzar remember last setting, especially 
'Encoding' option.

Thanks,
Okisan 

Original issue reported on code.google.com by kyawt...@gmail.com on 3 Jun 2009 at 8:04

• Blocking: #89

[GoogleCodeExporter]

Indeed, I remember you asking for this earlier. I will try to add it to the 1.8
release. My only concern is _where_ to save the data. I will probably put it in 
the
user's home directory. 
Also, I have to decide _which_ data to save. If we saved everything, someone 
could
get onto your computer and seriously mess stuff up (e.g., change word mappings, 
load
an empty model, etc.). 

Original comment by seth.h...@gmail.com on 4 Jun 2009 at 1:27

• Changed state: Confirmed
• Added labels: Type-Wishlist
• Removed labels: Type-Defect

[GoogleCodeExporter]

Thank Seth Hetu. Sorry if I requested again and again. It is much needed 
feature. :)

Yeah, it has to be robust. 

Original comment by kyawt...@gmail.com on 4 Jun 2009 at 1:31

[GoogleCodeExporter]

I've finally made a kind of "hierarchical" structure for config files. They 
should
work for both online users and regular users. A lot of the discussion regarding 
this
is located here:
http://code.google.com/p/waitzar/issues/detail?id=89

Changing status to "In Progress" --now that the new config files exist, I can 
save
user settings.

Original comment by seth.h...@gmail.com on 12 Jan 2010 at 9:41

• Changed state: InProgress

[GoogleCodeExporter]

In other news, we have a nice "settings" dialog. This will be relatively easy 
to hook up (but will require special "tagging" of local config file options, 
which isn't too hard anyway). We also "flash" the most recent settings to a 
small config file; we can read these on startup based on the main config file's 
option to load the "last" language.

We will also need:
  * a fallback mechanism for invalid "default" settings, in case the user removes a crashing plugin, etc. Now, the program will just revert to the default internal file. However, we should actually have a fallback to the "default defaults" (e.g., anything not defined in the local config file). Catching the exception is easy, but managing the configs will take some thinking.

Regardless, we can implement the standard behavior now and debug edge 
conditions once more code is in place.

Original comment by seth.h...@gmail.com on 18 Aug 2010 at 6:49

[GoogleCodeExporter]

I've added "last used" options for the following:
   * Input Method
   * Output Encoding

I still need to add "last used" for:
  * Language

After that, I will close this bug report. Note that Issue 13 will add a GUI to 
set these options (since it's kind of confusing). That issue is almost done 
too; after that, keeping the last-used language/etc. will be easy.

Original comment by seth.h...@gmail.com on 21 Sep 2010 at 10:14

[GoogleCodeExporter]

Language was added. Closing~~~

Original comment by seth.h...@gmail.com on 22 Sep 2010 at 3:42

• Changed state: Fixed