> No, this is not the way you do it. You just display the paint event once - it > stays up by itself and updates itself by itself. The standard way to do this > is to make a "draw_my_canvas( g as graphics)" method. You call it from two > places - your code when something changes on the canvas, and from the change > event of the canvas itself.
Yes, that's exactly what I was doing - it turns out there's a bug in RB that causes it to fire Paint events repeatedly when a window's Composite property is set to true and a PopUpMenu control is placed on the window. All I was doing was responding to those errant paint events, and trying to find out *why* they were being raised. Once I discovered the bug in RB I posted the bug report to the RB support site. Thanks! - John _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
