-
-
Notifications
You must be signed in to change notification settings - Fork 9.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ImGuiStyle serialization/deserialization #61
Comments
I'm not quite sure to understand the underlying desire here. I'd like eventually to add ImGui primitives to persistently store the kind of data that are used by tools. Simple end-user options, equivalent to making e.g. a Checkbox value persistent. So style may end up using that system. For now you could just dump the binary structure to a file using fwrite/fread, or use your own serialisation system. |
Yes, this is for the end-user and also I want to provide a default layout in my resources by copying imgui.ini. |
I agree there is a lack of features to manipulate window size/pos from code, it hasn't occurred to me but I suppose some people may be trying to steer away from the floating-windows size by enforcing certain size/pos. I'll add some primitives for that. |
I agree for windows manipulation. |
Resurrect old topic, the better window manipulation API was added in this commit: You have 6 calls, and the condition flag allows to set a value only once per session, or once if the data doesn't exist in .ini file, or always.
|
I am closing this issue seeing this one contains the same info Short answer - I am hesitant about encouraging the programmer to encourage the user to persistently manipulate their style. |
Hi Omar.
There is no way to save/restore style, a cool feature !!!
In a separate file or in .ini would be fine.
The text was updated successfully, but these errors were encountered: