I write a glade application for live video display,
and I have to refer to certain widgets which are initialized
at the `interface.c' file. I refer to them when the main menu
is activated, so these widgets are *not* the widgets of the
callbacks. This implies that I should transfer them to the
callback routines in a different way.
What I currently do is, manually change the `interface.c' file
to return pointers to the widgets I need, for later use:
create_gimage_app (GtkWidget **mainDisplay, GtkWidget **table1)
I think it should be possible for the user to mark which widgets
are "exported" from create_sth_app() for later use, and those
widgets would be added to the list of parameters of the initialization
routine. (A checkbox at the properties menu may indicate that
the user is willing to "export" this widget).
Maybe there is a different way to refer to these widget, and I'm
missing some point here? In any case, I don't want to start looking
for children of widgets which I just initialized.
Another comment: The numbers I enter (widget sizes, for example)
appear as numbers at the source code. Things could be much easier
if I had a list of constants (in `interface.c'?) which I could
include in other source files, to refer to these numbers.
For example, image size is used in many parts of the code.
The image size is identical to the size of the widget where the image
appears. If I change the widget size in `glade', I would expect it
to automatically affect the image sizes in the rest of the code.
Right now, if I don't change my constants manually, there will be
a contradiction...
-- Ariel.
P.S.: I'm not on this mailing list, so please CC me any reponse...
---
Ariel Tankus
Department of Computer Science
Tel-Aviv University
[EMAIL PROTECTED]
+---------------------------------------------------------------------+
To unsubscribe from this list, send a message to [EMAIL PROTECTED]
with the line "unsubscribe glade-devel" in the body of the message.
