[ Disclaimer: ]
Firstly, I'm sorry if this has already been covered in the list, or
elsewhere - I did look through the archives/docs and couldn't see
anything, but I know it's annoying to repeat stuff :-(
My first question relates to the way GLADE (I use 0.5.5) generates Help
menus. In the GLADE Menu Editor, there are stock items for _Help and
_About... but no label to assist with displaying information on help files
and manuals, etc.
For example, I am working on an app (as a small part of a university
project), called gSIC and need this code in my interface.c file:
/* ---------------------------------------------- */
static GnomeUIInfo help1_menu_uiinfo[] =
{
GNOMEUIINFO_HELP("gsic"),
GNOMEUIINFO_SEPARATOR,
GNOMEUIINFO_MENU_ABOUT_ITEM (on_AboutGSIC_activate, NULL),
GNOMEUIINFO_END
};
/* ---------------------------------------------- */
ATM, I just patch this by hand (now that the GUI design is pretty stable),
but it would be nice if GLADE handled it for me. Is this planned for a
future release (and if so will it be soon)?
I was considering a writing a patch to GLADE myself, but being a C newbie,
I couldn't quite work out how to go about this!
My second question relates to the way in which callbacks.c files are
generated. There are lots of "standard" callback routines that many GUIs
share - such as cut, copy and paste or callbacks relating to standard
GNOME tool bar items. Since much code like this will be present in the
examples section of the GLADE distribution (indeed, much code already is
there) I am curious as to why this sort of thing doesn't just get written
out to the calbacks.c file (perhaps optionally) when the source is built?
Is this a planned extension of GLADE, or have I misunderstood the
underlying philosophy?
Thank you very much in advance,
Sarah Mount.
--
http://snim2.robinson.cam.ac.uk
+---------------------------------------------------------------------+
To unsubscribe from this list, send a message to [EMAIL PROTECTED]
with the line "unsubscribe glade-devel" in the body of the message.
