That is perhaps the best-formatted post I have ever seen. Ever.

I think I'll start using that layout from now on.

Thank you very much [grin].

Edit: Make sure you put the < hr > tag and the text on the same line, or you'll get big chunks of space in between:

< hr >< center >[ b ]Title[ /b ]< /center >< hr >Paragraph goes here.

That's pretty similar to the layout I use in my header files, except I left align the heading texts.

Maybe I should start using a similar layout in my journal posts as well!

I figured I'd post it here instead of starting a new entry. I just did up some concepts on the user interface since I can't figure out how to do this fucking script editor =/. I'll talk to Raymond about it after he gets home from work.

Anyway, here's what most of the widgets on the list will look like:

Buttons


Choice Dialog


Counter


Listbox


Listview


Progress Bar


Tally Counter


TextBox


Listbox will hold only text items, whereas the Listview will hold anything based off of the Renderable class. Progressbars will be used throughout games (for healthbars and such). The Tally counter is for stuff like point allocation (i.e. in Baldur's Gate when you're choosing weapon proficiencies.) The choice dialog will consist of a listbox and 3 buttons. The buttons are optional.

Each widget is based off of a base widget class:

// basic OnMESSAGE methods
OnCreate
OnDestroy
OnRender
OnMove
OnResize
OnActivate
OnLeftClick
OnRightClick
OnMiddleClick
OnLeftRelease
OnRightRelease
OnMiddleRelease
OnMouseMove
OnMouseWheel

// OnDATAChange methods
OnTextChange
OnVisibilityChange
OnSelectionChange
OnStateChange

There are other things in the Widget class, but I haven't got all of that figured out.

The system includes a class called the Group. Its derived from widget and has 2 different forms: GroupBox, and Panel. GroupBox has graphical display qualities (like a Windows GroupBox). A panel on the other hand does not. The default settings for a Group is the panel setup. The system is pretty dependant on the user using the Group class.

Here's an example


With this code you have no idea which radio belongs in which group.



(See Telastyn, I told you I'd try [wink].)

With this pseudocode you can tell that the first 3 are in a group and the last 2 are in a different group. This also eases the code, since in the Group class, I can override the OnSelectionChange() and change each radio button status. This will also make it easier when I want to add tabs [grin].

Edit: I decided to go a little deeper in to this discussion. Grouping has been one of my major concerns, mostly because of the tab control and the radio button. I've had several different systems including different kinds of IDs, and a list of widgets that are grouped together stored within each widget (very bad idea). This system seems to work out very well and keeps with the design of the rest of the GUI code. You create and define a widget (by define I mean set it up) and then call Parent->Add(NewWidget). Something else that I didn't mention is that a Group also defines the area in which its children can be seen (its clipping rectangle.)