Re: Removing _construct functions when fixing _new() functions.
- From: murrayc t-online de (Murray Cumming)
- To: Owen Taylor <otaylor redhat com>
- Cc: GNOME2 Release Team <gnome2-release-team gnome org>, gnome-components-list <gnome-components-list gnome org>
- Subject: Re: Removing _construct functions when fixing _new() functions.
- Date: 15 Apr 2002 20:19:36 +0200
On Mon, 2002-04-15 at 20:00, Owen Taylor wrote:
> murrayc t-online de (Murray Cumming) writes:
> > Furthermore, it's very difficult to have the _construct() functions
> > _and_ the properties. If you refuse this then I will probably have to
> > remove the properties, meaning that libbonoboui will remain broken and
> > might never be usable from glade-like stuff.
>
> Well, one method of handling this is to improve the widgets so that the
> construct properties are not construct-only, so you can make your
> construct function simply set the properties in question.
Yes, they are already not construct-only, so this might be possible. But
here's another similar problem:
bonobo_window_construct() takes a BonoboUIContainer that was previously
instantiated in bonobo_window_new(). Now it's instantiated in the
*_instance_init() function, so what is bonobo_window_construct()
supposed to do with a 2nd BonoboUIContainer?
--
Murray Cumming
murrayc usa net
www.murrayc.com
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]