Visvis currently allows changing the settings using the visvis API. The
settings are stored in an ssdf file in the appdata directory.
It would be nice to be able to control this better, so that applications that
embed visvis can impose their own settings, or store custom settings to a
different file.
Some applications might also want to store extra settings. My feeling is that
these should be in a separate file, but maybe we can expose an API for that?
Further, we should look into how settings are dealt with in a frozen
application that uses visvis. You probably want to use the default setting, or
the settings that were present at freeze-time.
Original issue reported on code.google.com by almar.klein@gmail.com on 27 Aug 2012 at 11:09
Original issue reported on code.google.com by
almar.klein@gmail.com
on 27 Aug 2012 at 11:09