Update example to move setting window in frame.

[abreheret]

Update canny example to move the setting window :

[Dovyski]

Wow! Thanks for such an awesome pull request! Actually, your idea is so cool and useful to other users of cvui that it deserves its own example (independent of the canny one). And I can't stop watching the gif you provided 😃

I will merge your PR within the next days. Thank you!

[abreheret]

Cool that you like it ! Perhaps it would be better to put this class Setting in the lib cvui so that it is directly integrated into it ?
When I have free time I could do a PR of this class in cvui lib

[Dovyski]

I love the idea of integrating this feature into cvui, but it has to be done without classes. cvui follows a design where one call should produce one thing on the screen.

I was thinking that we could create a new window component whose X and Y params are pointers, so we can make the window move using that. What do you think?

[pthom]

Sorry to interfer, but I have one suggestion.

cvui's public API does not expose any classes; this is a design choice in order to be an immediate mode GUI. However, it might still use hidden classes inside its private implementation (inside the cvui::internalnamespace).

Thus, a possible implementation would be to store a dictionnary name->WindowOptions inside cvui::internal (something like map<string, WindowOptions> ?)

[abreheret]

Ok, I have not read the cvui source code yet, but i have that look at the use with the examples provided. I did not notice that classes were proscribed. So I do not know what would be the best way to integrate this feature. For my part, I must to read more deeply the source of cvui for better understand are internal work.

[Dovyski]

Ok, I have not read the cvui source code yet, but i have that look at the use with the examples provided. I did not notice that classes were proscribed.

That's totally my fault, I am sorry. A contribution's guide explaining those ideas is long overdue.

Thus, a possible implementation would be to store a dictionnary name->WindowOptions inside cvui::internal (something like map<string, WindowOptions> ?)

That's a possible solution if we want cvui to handle everything internally.