You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been looking for an opportunity to integrate this into my project. It appears currently, layouts have be generated at runtime from C++, it would be really great to be able to save layouts and load them as an asset.
The text was updated successfully, but these errors were encountered:
I'm not sure how would that work (I'm not saying it's impossible), as layouts work with pointers from C++, thus it would need to somehow serialize.
For what is worth, the layout system heavily borrows layouts from wxWidgets, and the best way (IMHO) to operate with it is to use wxFormBuilder to generate the widgets and layouts inside the editor, and the editor generates a piece of C++ (or XRC file) to generate the same widgets with that layout in your code.
For more advanced uses (e.g. where the UI is procedurally genrated), I still use wxFormBuilder as a template to cut and paste the original code into the real one.
As for Colibri, I still use wxFormBuilder to sketch the layouts and then I finally type the Colibri layout code by hand. Since the behavior is almost 1:1 (but not exactly) it is a very efficient method to quickly create new UIs.
Serializing both widgets and layouts together is much easier, than just layouts alone.
I have been looking for an opportunity to integrate this into my project. It appears currently, layouts have be generated at runtime from C++, it would be really great to be able to save layouts and load them as an asset.
The text was updated successfully, but these errors were encountered: