On Thursday 14 June 2001 10:51, Russell Nelson wrote:
> Edward Muller writes:
> > Yes, but those are different glade files. Aren't they? (Sorry I didn't
> > look).
>
> Yes, exactly.
>
> > My guess is that the ConfigureNotify X event (or whatever it is called)
> > needs to be built into gtk. Then if Gtk emits a signal when the X Event
> > is triggered you could put together a handler that would destroy all of
> > the existing widgets and then tell libglade to load a new file and
> > create a new set of widgets.
>
> Yep. Just what I want.
>
> > I don't think putting support for RandR directly into glade is the right
> > thing. Glade's purpose is to create a gui based on an XML file, nothing
> > more. Once the gui is created the rest is in the scope of the gui
> > toolkit.
>
> Libglade might be the right place to know about RandR, but it would
> have to either 1) know about multiple glade files, or 2) glade would
> have to be extended to deal with multiple resolutions in the same
> glade file. Ugh, ugh, ugh.
>
> The nice thing about putting it in libglade is that you'd be
> completely insulated from needing to know about screen resolution.
> But ugh, that doesn't work either, because an application is going to
> change its widget tree, if only by set_value().
>
> It's probably best put in gtk as a signal. Then you'd just write a
> signal handler to do what was necessary.
Yep, there are also other things you may want to change depending on the gui
your using as well, various .set_data functions you will need to re-setup
once the new widgets are in place, etc....
-- Edward Muller - edwardam@home.com - edwardam@handhelds.org Grow a ponytail -- view it as your telepathic antenna to other Linux Kernel Developers. -- Jeff V. MerkeyReceived on Thu Jun 14 09:03:24 2001
This archive was generated by hypermail 2.1.8 : Tue May 04 2004 - 09:38:26 EDT