A: In the GNOME version of Glade the Quick-Start Guide, Manual, and FAQ are available from the Help menu. Unfortunately these do not cover all aspects of using Glade yet.

There are a few other docs available on the web:

Spanish Guide - tigre.aragon.unam.mx/m3d/links_es.htm

Italian Guide - digilander.iol.it/robang/glade

I don't think there are any books specifically about Glade, though I have seen a chapter on Glade in a book from Wrox press for Linux developers.

I'll add links to documentation to Glade's home page at glade.gnome.org as they become available.

A: Glade includes a simple text editor example application in the examples/editor directory. If you have a binary-only package of Glade (e.g. an RPM), these files may possibly be installed in /usr/doc/glade-X.X.X. If you can't find it, download the Glade tarball from glade.gnome.org.

The web site contains links to quite a few applications created using Glade. These may contain useful example code. See the 'Applications' page on glade.gnome.org.

A: No. You are free to use whatever license you like for the C code generated by Glade.

Though in the spirit of free software we do encourage you to use the GPL or LGPL licenses.

A: This is not a bug in Glade! In GTK+ you use containers to lay out your widgets. The commonly-used containers are at the bottom of the main page on the palette. Try adding a vertical box to a window in Glade. Now add a table to one of the positions in the vertical box. Do you get the idea now?

If you really want to position widgets at specific coordinates, try the Fixed container. However, this isn't recommended since your windows/dialogs will not look good when resized, and if you translate the text in the labels and buttons into other languages they may not fit.

A: You can use standard GTK+ rc files to set the colors & fonts of your widgets. If you turn on the 'Set Widget Names' project option in Glade, that may make it easier to refer to your widgets, as you can refer to them by name. See the GTK+ Resource Files documentation at developer.gnome.org/doc/API/gtk/index.html.

You can also change a widget's style within your code by calling gtk_widget_modify_style(), e.g.

  GdkColor red = { 0, 65535, 0, 0 };
  GtkRcStyle *rc_style = gtk_rc_style_new ();
  rc_style->fg[GTK_STATE_NORMAL] = red;
  rc_style->color_flags[GTK_STATE_NORMAL] |= GTK_RC_FG;
  gtk_widget_modify_style (widget, rc_style);
  gtk_rc_style_unref (rc_style);
      

A: Create a button and select Remove Label from the popup menu. You can then add any widgets you like to the button, e.g. a horizontal box with a pixmap and a label inside it. (Glade may make this even easier in future.)

A: Hold the 'Control' key when you select the widget in the Palette. It will then stay selected until you select another widget or the Selector.

A: You can safely ignore this warning. It is output by GTK+ to remind people to update their code, since the behaviour of scrolled windows changed quite a bit between GTK+ 1.0 and GTK+ 1.2. But the Glade code is OK. The warning should not appear in your final application.

A: If you are creating a GTK+ application, your graphics must be in XPM format. (GTK+ 2.0 will include the gdk-pixbuf library and so will support many more graphics formats.)

If you are creating a GNOME application, most graphics formats can be used. Though the PNG format is preferred for most graphics such as icons.

You can convert images between formats using the GIMP graphics application or the 'convert' utility in the ImageMagick toolkit.

A: Follow these steps:

• Select the widget you want to add the handler to.

• Select the 'Signals' page in the Property Editor window.

• Click the '...' button to the right of the 'Signal:' field. This should show a popup window listing the signals that this widget emits.

• In the popup window, select which signal you want to connect a handler for and hit the 'OK' button.

• Glade automatically creates a name for the signal handler function in the 'Handler:' field, but you are free to change this if you desire.

• Click the 'Add' button to add it to the list of signal handlers for this widget.

When you generate the C source code, an empty signal handler function should be output in the callbacks.c file. You can add your code to this function.

A: You need automake >= 1.4 & autoconf >= 2.13 to build the generated C code. You also need gettext >= 0.10.35 if you enabled gettext support. See the Requirements section in the README file for links to these.

Run ./autogen.sh in the toplevel directory of the project to run automake, autoconf and the related utilities to build the Makefile's. Pass it any options you want passed to configure, e.g. ./autogen.sh --prefix /usr/local/gnome.

Then run make to build your application.

Note that for GNOME applications, you must also do a make install so that the pixmaps are installed properly. If you don't do that, it will still run, but you won't see the pixmaps.

A: This means that the gtk.m4 file cannot be found. (gtk.m4 is a set of m4 macros which is installed as part of GTK+ and is used to build programs which use GTK+.) aclocal (part of automake) searches for these macros to add to aclocal.m4 in your program's root directory.

To find out where GTK+ is installed, run gtk-config --prefix. The gtk.m4 file should be in the share/aclocal subdirectory. To find out the directory that aclocal is using, run aclocal --print-ac-dir.

You should add the directory that the GTK+ m4 file is installed to the ACLOCAL_FLAGS environment variable, e.g. if the GTK+ m4 files are in /usr/local/share/aclocal, then add this to your $HOME/.profile: export ACLOCAL_FLAGS="-I /usr/local/share/aclocal/".

A: You are trying to use Gnome stock menu items in a GTK+-only app. Edit any menus you have and make sure the "Stock" property is set to "None" for every item.

A: These are the default output files, but some of your file names may differ if you have changed the project options.

If gettext support is enable, the po directory is created, with POTFILES.in and a separate ChangeLog. POTFILES.in lists the source files which contain translatable strings, and you should add any source files you create here.

For GNOME projects the macros directory is also added, containing all the m4 macros used to build the project. (These should really have been installed as part of GNOME, but unfortunately this wasn't done in GNOME 1.0.X. Hopefully this will be fixed in a future version of GNOME, and so this directory will not be needed.)

If you change the Gnome Support or Gettext Support project options after building the project, you will need to update some of the build files such as configure.in and Makefile.am. The best solution may be to change the project directory in the Project Options dialog, and to rebuild the project from scratch. However, you would have to copy over any code you have added to signal handlers. An alternative would be to delete autogen.sh, configure.in, Makefile.am, src/Makefile.am, and src/main.c and use Glade to recreate them. But if you have changed these files you will need to add the changes back in. (Hopefully Glade will deal with this better in future.)

A: Glade will not overwrite most of the files. It will recreate the build files if they don't exist (and the corresponding project option is set.)

The files which Glade overwrites are: interface.h, interface.c, support.h, and support.c. (Though you may have named them differently in your project, if you changed them in the Project Options dialog.)

These files all have a warning at the top saying "DO NOT EDIT".

If you have added or updated any signal handlers, then these are appended to the callbacks.h and callbacks.c files. So any code you have already added for callbacks is completely safe! If you have renamed a handler function then it is up to you to remove the old version and copy any code to the new function.

A: Add the source file (and any header file) to src/Makefile.am, in the project1_SOURCES variable (where project1 is the name of your project).

If you are using gettext, you may also want to add the source file to po/POTFILES.in so that the strings can be translated.

A: You need to add a test for the library in your project's configure.in file, making sure that the CPPFLAGS and LIBS are updated to account for the library. (The CPPFLAGS variable should contain any -I flags to pass to the C preprocessor, and the LIBS variable should contain the -l and -L options to pass to the linker.)

autoconf provides macros such as AC_CHECK_HEADER and AC_CHECK_LIB which can be used to check for general headers and libraries.

Many GTK+ and Gnome libraries provide a config script such as gtk-config which will output the CPPFLAGS and LIBS flags needed.

For example, libxml provides an xml-config script which you can use like this:

  dnl Get libxml flags & libs
  AC_PATH_PROG(xml_config, xml-config)
  if test "x$xml_config" = "x"; then
    AC_MSG_ERROR([*** xml-config not found.])
  fi

  XML_CFLAGS=`$xml_config --cflags 2>/dev/null`
  XML_LIBS=`$xml_config --libs 2>/dev/null`
  CPPFLAGS="$CPPFLAGS $XML_CFLAGS"
  LIBS="$LIBS $XML_LIBS"
      

Make sure you place your configure.in test before the call to AC_OUTPUT.

A: Use the lookup_widget() function provided. (It can be found in support.c.)

You pass it a pointer to any widget in a window, and the name of the widget that you want to get. Usually in signal handlers you can use the first argument to the signal handler as the first parameter to lookup_widget(), e.g.

void
on_button1_clicked                     (GtkButton       *button,
                                        gpointer         user_data)
{
  GtkWidget *entry1;

  entry1 = lookup_widget (GTK_WIDGET (button), "entry1");

  ...
}
      

Note that this does not work if you are using libglade. The corresponding code for libglade would be:

void
on_button1_clicked                     (GtkButton       *button,
                                        gpointer         user_data)
{
  GladeXML* xml;
  GtkWidget* entry1;

  xml = glade_get_widget_tree (GTK_WIDGET (button1));
  entry1 = glade_xml_get_widget (xml, "entry1");

  ...
}
      

A: You need to keep track of pointers to all your toplevel windows. For simple applications you can just use global variables to store these pointers.

For more complicated applications you can use gtk_object_set_data() and the related functions to store a pointer to one window inside another window. For example, if you want to create a dialog which needs to access widgets in the main window you can do this:

  dialog = create_dialog1 ();  /* Call the function generated by Glade. */
  gtk_object_set_data (GTK_OBJECT (dialog), "main_window", main_window);
      

  main_window = gtk_object_get_data (GTK_OBJECT (dialog), "main_window");
      

You need to be careful to ensure that the pointer is always valid. If the window being pointed to is destroyed, make sure you no longer use the pointer to it or your application may crash.

A: Call gtk_menu_get_active() with the GtkOptionMenu's menu to get the currently selected menu item. You can use g_list_index() to find its index in the menu:

void
on_button1_clicked                     (GtkButton       *button,
                                        gpointer         user_data)
{
  GtkWidget *option_menu, *menu, *active_item;
  gint active_index;

  option_menu = lookup_widget (GTK_WIDGET (button), "optionmenu1");
  menu = GTK_OPTION_MENU (option_menu)->menu;
  active_item = gtk_menu_get_active (GTK_MENU (menu));
  active_index = g_list_index (GTK_MENU_SHELL (menu)->children, active_item);

  g_print ("Active index: %i\n", active_index);
}

A: Glade doesn't support this at present, but you can set it up manually.

When you create the window, get the option menu and connect to the "deactivate" signal emitted by its menu:

  window1 = create_window1 ();
  option_menu = lookup_widget (window1, "optionmenu1");
  gtk_signal_connect (GTK_OBJECT (GTK_OPTION_MENU (option_menu)->menu),
                      "deactivate", GTK_SIGNAL_FUNC (on_option_selected),
                      NULL);

Then add a handler to callbacks.c. You can get the index of the selected item just like the previous answer:

static void
on_option_selected (GtkMenuShell *menu_shell,
                    gpointer data)
{
  GtkWidget *active_item;
  gint item_index;

  active_item = gtk_menu_get_active (GTK_MENU (menu_shell));
  item_index = g_list_index (menu_shell->children, active_item);

  g_print ("In on_option_selected active: %i\n", item_index);
}

A: Glade doesn't support this at present, but you can set it up manually, in a similar way to question 3.6.

When you create the window, get a pointer to the widget containing the adjustment, and connect to the "changed" or "value_changed" signals:

  window1 = create_window1 ();
  hscale = lookup_widget (window1, "hscale1");
  gtk_signal_connect (GTK_OBJECT (GTK_RANGE (hscale)->adjustment),
                      "changed", GTK_SIGNAL_FUNC (on_adjustment_changed),
                      NULL);

A: After you create the window, using the 'create' function generated by Glade, use lookup_widget() to get a pointer to the GtkCList widget, and add the rows as required. e.g.

  GtkWidget *window, *clist;
  gchar *row[2];		/* Our GtkCList only has 2 columns. */

  window = create_window1 ();
  clist = lookup_widget (window, "clist1");

  row[0] = "Hello";
  row[1] = "World";
  gtk_clist_append (GTK_CLIST (clist), row);

  row[0] = "Second";
  row[1] = "Row";
  gtk_clist_append (GTK_CLIST (clist), row);

  gtk_widget_show (window1);