> > 2. Introduce Zorder as one of the properties in pdict and modify the > > internal _dlist to refer to Zorder on a draw where the property > > exists. > > I'm not sure about this one -- I don't really see zorder as a property > of the DrawObject itself, but rather a property of the Canvas it's on -- > or the "Document" or layer, or something. Part of this idea comes from > how I've always envisioned that the same DrawObject could exist outside > of any Canvas, and perhaps be on more than one canvas at once. > > I have thought about how there really should be some sort of "Document" > or "Drawing" object that FloatCanvas uses to keep track of the > DrawObjects, rather than just a couple lists, like it has now. This > would provide a place for code to save the Drawing, and perhaps code to > manipulate z-order and the like. To start, I think it could just be a > class with a _DrawList and _ForeDrawList attributes (and few others, > like maybe the various "Dirty" flags. > > Whether or now we do that, I've always intended to have methods like: > > MoveObjectToTop > MoveObjectToBottom > ShiftObjectUp > > etc. > > On the other hand, in some applications some sort of z-order value could > make sense -- if it's optional, then it won't hurt anything.
I too need a way to order how objects are drawn. See the new "Layers in wxFloatCanvas" thread. Could use your input into that. Tim 'Mithro' Ansell _______________________________________________ FloatCanvas mailing list [email protected] http://mail.mithis.com/cgi-bin/mailman/listinfo/floatcanvas
