A widget messaging system has no need to pass any data around at all. You get the message from the widget, decide what to do based on which widget and what message it is, and then you do it. It makes it far easier to deal with an action locally as opposed to globally or wasting your time binding a 1000 different sets of data into 1000 different structs and having a custom callback function for each of your 1000 different structs.

Fixed X 2.

Possibly. Depends on whether you intend to re-use that function or not. If you do, best not to touch global data!

That's again debatable, but it's not what you said earlier where you claimed you "have to use global data".

It's ok, you don't like the A4 GUI. You don't have to either, and you don't have to rationalise it as far as I'm concerned. If you do though, at least keep your arguments consistent.

That piece of code looks pretty obscure to me though!

Not even for the sake of those who like the A4 GUI? But don't worry, I'm sure that eventually different people will make different GUI addons since there's clearly room for different approaches here.
As I already said earlier, using A5's event system to interact with the GUI makes the most sense to me if you're designing the GUI from scratch. That's actually not orthogonal to basing the GUI on Allegro 4's GUI though.
Also, to get back to an earlier point in the discussion, it doesn't require C++ either (Allegro 5's event system is C, afterall).

Fair enough.

Yeah well, consider me proven wrong. SiegeLord's and Matthew Leverton's designs seem reasonable enough to me. Still, using a this pointer seems rather archaic now that I use C++.

That's because you're travelling quicker than the light, Evert.

The example program doesn't actually seem to show me any GUI widgets. I don't know if it's because my Makefile is doing something wrong or if I'm just not using the program properly. Should it be drawing something? What platform(s) have you tried it on? Or is it just an empty shell right now that needs to be filled in?

OK, now I see. Thanks.

I was wondering about that. I just wasn't going to be the one to say anything.

I'm making a C++ GUI lib with the following features.
Editor, save and load XML layouts.
Skinning, code your own rendering routines or customize data for existing routines.
Event queue, widgets put events in a queue and lets you handle them where you want.
Layout, container widgets that handle size and position of their children.
Clipboard, copy text between your application and the rest of your OS.

And possibly more coming. Of course, even this basic list of features are under rather slow development since I have a full time coding jorb and is very tired in the evenings.

I named the project SWAG.

For now, the example program is the testing ground for the new features. It currently tests drawing, widget tree management, focus and layout management.

I will change it then, but in the future.

It would be nice to have a few official A5 GUI libraries to choose from...
But I guess GUI libraries is just another 'touchy' topic.

Killed me.. So true, in Israel and many many other countries- it's the same.. However, I wonder how it goes if they film it, if they're allowed to and, or.. ? Kinda it's obvious that port would not be allowed to be sold cos' the actors have to be over 18 as well, but if they shot it(didn't look at it for 2 years), why the hell can't they sell it afterwards?!

P.S:
I add me "+1" to the nomination of this thread to Allegro '11 derail rewards..