On 4 October 2012 03:06, Dimitar Zhekov
<dimitar.zhekov@gmail.com> wrote:
On Tue, 2 Oct 2012 13:03:00 +1000
Lex Trotman <
elextr@gmail.com> wrote:
> Are all settings saved on apply? not just the prefs/project prefs ones? I
> thought there were some that still didn't for one reason or another, maybe
> that should be changed as a separate thing anyway, in which case you are
> right, the "rush" only applies to session data.
dialog preferences, UI settings and file list.
Project -> Properties -> OK saves the entire $project.conf: project
settings and file list.
File -> Quit does both.
AFAICT build->set build commands->ok does neither, it assumes save at the end, thats the problem, and why the save on quit is still needed and why failing to save on shutdown is a breakage.
The build one is the one I know, my question is then what other dialogs or menu items etc change settings but fail to cause a save because they still assume save on exit?
Saving dialog preferences and project settings on Quit does not make
real sense, but it's the same file, so there is no reason to separate
them. Yet they are internally separate (static) functions, see
keyfile.c:configuration_save() and project.c:write_config().
Not sure what you mean by "its the same file", its not the same file and doesn't have the same contents?
Cheers
Lex
--
No interest in having 2+ sessions for a project?..
--
E-gards: Jimmy