Yes, that's another point, a readable uisettings.ini format would be great, even though I decoded much of the current format by now (the info is somewhere in Landiin's UI settings spy thread I think).
Quote:
Originally Posted by SOE-Rothgar
Thats a possibility too. If someone wants to write up some details on how they'd like to see it work, I'd love to take a look at it.
|
I would basically like the possibility to store arbitrary information (mostly integers) to a file for window configuration. For example, currently in my ControlCenter window you can scale the target effect icons. I would like to be able to store that setting so I can restore it next time the user logs in.
There are two very easy ways to implement this:
- Since I don't assume that you will just give us the possibility to save to arbitrary files (for security reasons), maybe just give us the possibility to save to one specific file, eg. eq2ui_custom_settings.xml.
The functionality would be very simple. We can load that file during runtime and make modifications via ui scripting just like we currently do. The only thing you would need to add is that we get the command /save_custom_settings (or something like that) and that will take the version of that xml which is in memory and write it to disk.
- The alternative implementation to that would be to have /save_uisettings also save changes made to windows via scripting. For example, if I set window size and position via a script it will not save unless I modify the window with the mouse first. If I could have the script modified settings saved via a script triggered /save_uisettings, then I could also store integer values by manipulating the size and location of elements.
And while you are taking wishes, fix the scripting engine to allow the handling of non-ascii characters, and give us dynamic data for raid wide impairments.
