Re: Reverse-wrapping gtkmm widgets to gtk+ (for glade3)
- From: Murray Cumming <murrayc murrayc com>
- To: Alexander Brinkman <a brinkman marin nl>
- Cc: gtkmm-list gnome org
- Subject: Re: Reverse-wrapping gtkmm widgets to gtk+ (for glade3)
- Date: Tue, 21 Nov 2006 20:54:37 +0100
On Tue, 2006-11-21 at 20:50 +0100, Alexander Brinkman wrote:
> On Tue, 2006-11-21 at 09:15 +0100, Oliver Nittka wrote:
> > ok, well, except libglade does not seem to honor the saved properties:
> > when setting the property in simpledraw.glade, the widget always shows
> > up with showblue's default state (no matter how you initialize showblue
> > in the c'tor).
> >
> > well, let's tackle this one, too! :-)
>
> You can dodge this with glade's register custom prop functionality. See:
> http://developer.gnome.org/doc/API/2.0/libglade/libglade-Libglade-Build.html#glade-register-custom-prop
>
> I've tested it, and my custom property function is indeed called after
> instantiating the widget, so it could work (I've only done a quick test
> as I had little time today).
>
> However, perhaps someone familiar with Glib::Property's knows why the
> property isn't set the normal way. I mean: Glade3 seems to supports the
> property directly, and even libglade knows whether the gtkmm widget has
> the named property (because else libglade starts complaining that the
> property does not exist).
Yes, that should work. I guess it needs someone to look at the Glade
source and see what's happening. For instance, to find out why the
property is not saved in the .glade XML.
--
Murray Cumming
murrayc murrayc com
www.murrayc.com
www.openismus.com
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]