On Sun, Jan 17, 2010 at 19:43, Michael Hutchinson <[email protected]> wrote: > On Mon, Jan 11, 2010 at 6:51 PM, Piotr Zurek <[email protected]> wrote: > Because you're only using the child in a very limited way, you can > probably just subclass Bin and stuff the child in that, so it does the > bulk of work of propagating mapping, realization, destroying, etc. to > the child. Then, on the expose event of your widget, you have to check > the child state depending on the state of your widget. You may have to > set its visible state, or give it a requisition if its position has > changed, then propagate the expose.
That sounds like what I had in mind, because this approach means that I can pretty much bolt it on what I already have. > I think the Medsphere GTK# widget have some containers written in > managed code you could look at. I'll definitely have a look at those widgets. Thanks again. -- Piotr http://piotrzurek.net http://twitter.com/pzurek _______________________________________________ Gtk-sharp-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/gtk-sharp-list
