Mike Perry wrote:
>
> I have a beef with the custom widget creation function. Why must it only
> take constant strings and integer values as arguments? I find this extremely
> inconvient. I have a widget and I need to pass it a dynamic string (as in a
> a string in a variable or a #define) and glade won't let me do this. (It keeps
> putting the variable in quotes). Also, I need to be able to pass it a pointer
> to a text entry widget it needs for callback info, but glade only allows
> constant integers..
I think it is a bad idea for the interface definition to contain C code
(i.e. macro names, variable names etc.)
> Why strings and ints at all? Wouldn't things be much more extensible if you
> just kept up the GTK+ tradition of a gpointer *user_data argument (or even 4
> gpointers)?
>
> To give you an idea of how inconvient this is to me, right now I'm creating
> two realize signal handlers for one of the windows. One takes the widget I
> need as an argument and assigns it to a global variable to be used by my
> custom widget, and the other does the same with the dynamic string... Pretty
> annoying :)
You should probably be using the lookup_widget() function to access widgets,
or attaching data to widgets with gtk_widget_set_data_full() etc.
Damon
+---------------------------------------------------------------------+
To unsubscribe from this list, send a message to [EMAIL PROTECTED]
with the line "unsubscribe glade-devel" in the body of the message.
