Note: I am using v2.1 ZERO (the free one) if these issues are solved in the ONE version (the paid one) please let me know.
Right now the way the export works in the tool is to generate what is effectively an example program template with the GUI stuff filled in based on the layout. I believe this limits the utility of rGuiLayout because it makes it difficult to iterate on existing layouts and programs that have had significant amounts of work done to them already.
I think it would be helpful to have an option to break apart the generated file into the raygui specific portions into something like the below set of files.
This way the user of rGuiLayout can position their exported code within their projects how they see fit and reduce potential for copy-paste errors when moving the exported code into existing projects and exported layouts.
Note: I am using v2.1 ZERO (the free one) if these issues are solved in the ONE version (the paid one) please let me know.
Right now the way the export works in the tool is to generate what is effectively an example program template with the GUI stuff filled in based on the layout. I believe this limits the utility of rGuiLayout because it makes it difficult to iterate on existing layouts and programs that have had significant amounts of work done to them already.
Here is an example export with a few controls:
I think it would be helpful to have an option to break apart the generated file into the raygui specific portions into something like the below set of files.
control_function_declarations.h
control_data.h
control_drawing.h
control_function_definitions.h
This way the user of rGuiLayout can position their exported code within their projects how they see fit and reduce potential for copy-paste errors when moving the exported code into existing projects and exported layouts.
Thank you for your consideration.