no key, but surge writes presets into subfolder(s).
OK, I think I can implement read-only settings retrieval from the DLL folder - this can be used for key storage, for example. I won't implement settings writing for the reason I've mentioned so that nothing breaks. However, Application Data file will be of higher priority, so that you can still make changes to the setting retrieved from the DLL folder with the exception that the newer setting will be stored and retrieved from the Application Data folder. If this is unsatisfactory to you, I may simply skip implementing it at all.
In the future I may also switch to a single settings file instead of bunch separate setting files, but this is of no priority.
or maybe you can check the os version to only store it in application data folder if the user is running vista (otherwise store in dll folder)?
cool, many thanks!
This topic was last updated 180 days ago, and thus it was archived. Replying is disabled for this topic.