Dermot Musgrove wrote:
>
> Hi all,
>
> A couple of thoughts, please excuse me if some of this does not make sense
> immediately but I program in perl and not C :-)
>
> 1) There are two types of <signal> elements with different purposes
> a) signal to handler definitions
> b) <accelerator> definition of signal to emit
> Might not b) be <emit_signal>
Isn't the usage easily determined by the context? i.e. if it's inside a
<widget> then it is a signal handler, if it's inside an <accelerator> it's
the name of the signal to emit.
What do others think? I don't mind changing it, but Glade would have to
support the current tags anyway for backwards compatability.
> 2) Prior to the Gnome version, <child_name> elements all had the same name
> as the method that acquired a ref to them.
I don't think that is correct. The names were just used to identify the
widgets. You need to add special code for each widget to turn this name
into a pointer to the particular widget. And some of the names, e.g.
'CList:title', 'Notebook:tab' can be used more than once to iterate through
the children.
> Unfortunately, some of the Gnome
> widets are different. For example, the gnome_entry child_name is
> GnomeEntry:entry but the method to get a ref to the entry widget is
> gtk_entry and gnome_pixmap_entry has methods
> gnome_file_entry, gnome_entry and gtk_entry - none of which match the
> child_name of GnomePixmapEntry:file-entry (and it has a minus sign rather
> than an underline)
I should probably have called it 'GnomePixmapEntry:file_entry' but I'm not
sure its worth changing.
Damon
+---------------------------------------------------------------------+
To unsubscribe from this list, send a message to [EMAIL PROTECTED]
with the line "unsubscribe glade-devel" in the body of the message.
