Just agreeing with Rook Zimbabwe, this is a portion of an INI file which defines my UI for one of my screen (exit screen).
(Not quite a resource file, but better than hard-coding.)
[PAGEQUIT]
1= panel, plinth,, ,, 300,240,500,360,
2= mess, text,FNTSTDM, ,, 310,290,490,310, Do you want to exit?
3= yes, button,, QUIT,yes, 340,330,390,350, Yes
4= no, button,, GotoPage,PageBrMenu, 410,330,460,350, No
This way I can alt-tab, change a value, alt-tab back, press an F-key which reloads the UI parameters, and I can immediately see the change.
Not as elegant as a dialog with choices, but practical.
For anyone who isn't sure how to store UI params, I'd recommend using INI-files.
You can always write a front-end for that system later.
(Not quite a resource file, but better than hard-coding.)
[PAGEQUIT]
1= panel, plinth,, ,, 300,240,500,360,
2= mess, text,FNTSTDM, ,, 310,290,490,310, Do you want to exit?
3= yes, button,, QUIT,yes, 340,330,390,350, Yes
4= no, button,, GotoPage,PageBrMenu, 410,330,460,350, No
This way I can alt-tab, change a value, alt-tab back, press an F-key which reloads the UI parameters, and I can immediately see the change.
Not as elegant as a dialog with choices, but practical.
For anyone who isn't sure how to store UI params, I'd recommend using INI-files.
You can always write a front-end for that system later.