Generally, the program grabs global settings (all settings, in fact) as it
needs them. This is fine in most cases, but not for others. The HSQLDB
module, for instance, grabs the data output directory at startup and never
checks it again. If the user wants to change the location they keep their
data, they have to make the change and restart the program. This is
somewhat counterintuitive.
PROPOSED FIX:
Define a settingsUpdated() method in one of the module classes and
implement it each of the modules. For most of them, it would be empty. We
could then call the settingsUpdated() method when the settings dialog is
closed.
Original issue reported on code.google.com by cropplan...@gmail.com on 1 Apr 2008 at 2:38
Original issue reported on code.google.com by
cropplan...@gmail.com
on 1 Apr 2008 at 2:38