On Thu, 2008-07-24 at 21:22 -0700, Pieter V. wrote: > Feel free to correct me if I'm wrong, _why. > > > The first argument is the Widget's parent Canvas, and the second is a > boolean flag describing whether the current call to #draw is for > buffering or "actual" output. The relevant code (if you feel up to > some digging is around canvas.c:1156.
Thank you Pieter. Of course it's in Canvas! I would have found it eventually. I might get this widget to work yet. Thank you for the clues. _why?, Canvas base classes don't seem to be documented. > > > As for the second question, I haven't verified it myself, but would > #repaint_all meet your needs? That would be nice, but from inside a widget's method I get a 'no method' error for repaint_all, but I know where to look now for my clues. > > > -- pvande > > On Thu, Jul 24, 2008 at 8:59 PM, Cecil Coupe <[EMAIL PROTECTED]> > wrote: > Does anybody know what those two args to Widget.draw() are? > > Or the magic method name for triggering a repaint on a > stack/flow? In a > Widget? > > --Cecil > > >
