Gonzalo Aguilar Delgado wrote:
1.- Passing a data structure
2.- Using global variables (not good threading support)
3.- Passing window to gpointer and searching.
But the point is.
What is the best way? Is there any other way to do that? Because
structure option looks
This way is one of the best I found.
Ensures compatibility and as you said performance impact is minimum.
Anyway, I found that using a mix of this way and using user data to set
widget pointers is a tradeof between performance and memory consumption.
So I set the widget dependencies with:
hi,
Gonzalo Aguilar Delgado wrote:
Yep, I know about some of them:
1.- Passing a data structure
2.- Using global variables (not good threading support)
3.- Passing window to gpointer and searching.
4.- Use GObjects for you UI
In my apps I don't directly insert
Hi, stefan.
This looks also good but it's a pain to have to instanciate every
widget. But for some special widgets may be a great solution...
Thank you for your reply.
hi,
Gonzalo Aguilar Delgado wrote:
Yep, I know about some of them:
1.- Passing a data structure
2.- Using
Hi Gonzalo,
I don't do that for *every* widget, just for logical groups.
In my GUI application I do this for the window, the toolbar, the statusbar, the
content area (a notebook) and for each content page. Likewise I subclass dialogs.
Stefan
Gonzalo Aguilar Delgado wrote:
Hi, stefan.
This
On Tue, Mar 28, 2006 at 09:38:20AM +0200, Gonzalo Aguilar Delgado wrote:
Because receiver callback is getting only the receiver widget,
In addition, the callback gets an arbitrary pointer passed
as user_data to g_signal_connect(). A pointer can be used
to pass anything.
This is a very
