Deborah> Could you give examples of the use of those functions?
Sure. Below is a short routine that gives a few examples. There are some
things I haven't quite figured out how to do without knowing the internals of
the GtkArg structure (i.e. set callbacks).
BTW, the only problem with this
On Mon, 21 Aug 2000 [EMAIL PROTECTED] wrote:
>
> Hi there...
>
> I am creating an app using GTK+... I don't like global variables, or
> exporting large numbers of variables to implement functionality.
>
> I have a form with multiple entries and combos and spin-buttons and I
> would like to be
On Mon, Aug 21, 2000 at 02:32:58PM -0400, [EMAIL PROTECTED] wrote:
> I'm thinking something along the line of using a function on the
> top-level widget to return a pointer to the requested child-widget
> (requested by name, since I did name all my widgets, and whats the
> point of names if this
> Luckily, GTK+ already has the equivalent, and I pretty much use them instead
> of separate get/set functions: gtk_widget_set(), gtk_widget_setv(),
> gtk_widget_get, and gtk_widget_getv().
Could you give examples of the use of those functions?
Debby
-> In my personal view, those set and get functions lead to code bloat
-> that I don't need. I'll admit to not having actually tested my
-> opinion, but I'm not getting paid to do this and I'm happy with my
-> coding style.
Derek> You could always access the struct component
-> If GTK+ were actually object oriented then all that work would already be
-> done.
[Entering into the realm of conjecture and tit-for-tat Comp Sci
definitions here...]
Depending on your definition, GTK+ is objected oriented. It has
inheritance, classes, a type system, and mor
Well Derek
If GTK+ were actually object oriented then all that work would already be
done. As for "standard object-oriented design"... ummm, I didn't say that
was my design objective, I just don't like global variables... =)
In my personal view, those set and get functions lead to code bl
-> I am creating an app using GTK+... I don't like global variables, or
-> exporting large numbers of variables to implement functionality.
Standard object-oriented design says to write _set_ and _get_
functions for each variable you wish to have publicly r/w. I.e.,
gint config_page_get
Hi there...
I am creating an app using GTK+... I don't like global variables, or
exporting large numbers of variables to implement functionality.
I have a form with multiple entries and combos and spin-buttons and I
would like to be able to access those widgets without having a global
variable
