On 4/7/07, Craig Pemberton <[EMAIL PROTECTED]> wrote:
> I just discovered lookup_widget()!
If you're using lookup_widget(), that means you're using Glade's code
generation, which is going away in glade 3. Use libglade instead,
especially if you're not too far into your project.
-Jim
__
On Sat, 2007-04-07 at 05:15 -0500, Craig Pemberton wrote:
> I just discovered lookup_widget()! This makes life much easier. The code now
> looks like the following. I'm not sure if this is best, but I used it by
> getting the parent and then using lookup_widget() to look through it's
> children.
>
Hello Everyone,
I am looking advice on how to structure the gtk application I am working on.
I think that it lends itself very well to the signal/callback mechanism but
I am not sure and would hate to waste time.
The program is going to be a diagnostic heads up display for an autonomous
vehicle.
I just discovered lookup_widget()! This makes life much easier. The code now
looks like the following. I'm not sure if this is best, but I used it by
getting the parent and then using lookup_widget() to look through it's
children.
I'm happy with this code now. Thanks again.
//This event is called
Thank you so much Andrew!
It is now working beautifully. The final code is below for anyone who may
read this thread looking for the same fix.
void on_toggletoolbutton_enable_toggled( GtkToggleToolButton
*toggletoolbutton, gpointer user_data )
{
GtkTable *parent = (GtkTable*)
gtk_widget_
On Fri, 2007-04-06 at 23:45 -0700, Craig Pemberton wrote:
> GList *children = g_list_first(parent->children);
For starters, you want
gtk_container_get_children()
From there, you might also double check you're using the GList API
properly.
AfC
Sydney
___
