Re: ORBit2 and async stuff
- From: Ettore Perazzoli <ettore ximian com>
- To: Martin Baulig <martin home-of-linux org>
- Cc: Michael Meeks <michael ximian com>, gnome-components-list gnome org
- Subject: Re: ORBit2 and async stuff
- Date: 25 May 2001 21:03:59 -0400
> > If we have a getControl, we should have a setControl too, but I'm
> > not quite understanding how this should work.
>
> That'd be evil. A GNOME::Selector is a Bonobo::Control, more or less. We just
> cannot use queryInterface("Bonobo/Control") on the GNOME::Selector (according
> to the docu, you must not call bonobo_object_add_interface() after the object
> has been exposed to the outside, but the control cannot be created before the
> selector is fully constructed). So for the moment there's a getControl() method
> even if it's basically doable by QI.
This sounds really bad. The right way from an API standpoint is to
just have a control factory, and have the application QI for
GNOME::Selector to manipulate it.
For one, your method wouldn't work with GUI builders.
--
Ettore
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]