to code or not to code
In most cases, you can design a GUI without writing a line of code. You might not even have to look at the code GuiDesigner wrote. To interact with the GUI, all your program does is send messages to grid functions and receive messages from grid functions.
What messages do your programs send to achieve a particular result? The same ones GuiDesigner puts in the grid functions it creates from your design windows. Which means there's an easy way to learn how to do it yourself.
Let GuiDesigner show you. Build a window interactively, then look at the code GuiDesigner generates from it. Change the design a little and look again. Change it again and peek again. Learn as you go.
The code GuiDesigner puts in the Create subroutines is the same as the code you need in your program to control grids at runtime. Which means you can make GuiDesigner do your work for you.
Say you need code to change the color and text on an XuiLabel grid at runtime. Create a design window, give it a name, select an XuiLabel from the toolkit, bring up the AppearanceWindow, and give the XuiLabel new colors and a new text string.
Then select W indow T oFunction to make GuiDesigner create a grid function from the design window. You'll have no trouble finding the code that accomplishes what you want in the Create subroutine. Copy the relevant lines, paste them into your function, then delete the cheater window and function. Who needs 'em? You got what you wanted. Right?
By stealing code GuiDesigner writes, you can learn just about everything there is to know about writing code to control grids at runtime. It's not even a misdemeanor in most jurisdictions! After a few capers you'll see how simple runtime code is, and you'll realize how easy it is to write yourself. You'll be a pro in no time.