myself, I prefer the former, because I already know it exists if I've
worked with wxPython before. it's consistent.
with wxPython in general, when doing multiple modifications (and I don't
want the user to see half-done changes, or waste time displaying them),
I wrap my code with Freeze / Thaw. I see the ideal world as one in which
I never need to call the Draw method on the canvas, simply because the
other wxPython controls don't work that way.
the only control I can think of offhand that doesn't adhere to this is
the wxGrid widget (which is an oddball in more ways than this). wxGrid
has BeginBatch and EndBatch methods, which as far as I can tell are
functionally equivalent to Freeze and Thaw, but named differently. also
bad, but at least the paradigm is the same.
so under the principle of least surprise, there's my vote. ;)
thanx,
ryan
Christopher Barker wrote:
Ryan Blazecka wrote:
would the wxPython Freeze / Thaw paradigm be appropriate here?
It sure would. It comes down to taste, I think. Would you rather do:
Canvas.Freeze()
.. a bunch of changes
Canvas.Thaw()
or:
... a bunch of changes
Canvas.Draw()
(note that the later is the current approach, so it would not be a
backward compatible change)
thoughts?
-Chris
_______________________________________________
FloatCanvas mailing list
[email protected]
http://mail.mithis.com/cgi-bin/mailman/listinfo/floatcanvas
