As I understand it, with a single canvas, I'll need to compute coordinates differently for each dice pair and each die dot. The present scheme, with a Canvas per dice pair, calculates the coordinates of constituent elements relative to the local canvas and proportional to its size, so it's quite simple, and (I thought) elegant. I didn't mention earlier that there are 4 sizes of dice pairs. It seems to me that the '1 large canvas' approach leaves me with a lot of management of indexes, scale factors, and offsets. Is there something I can do with Control Order to get the system to overlay these controls and images without painting backgrounds back on top? Paul
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Joseph J. Strout Sent: Monday, April 03, 2006 9:35 AM To: REALbasic NUG Subject: Re: Canvas, Rectangle Shape, Paint Event confusion At 7:55 AM -0700 4/3/06, Paul Mathews wrote: >It seems ironic to me: In VB, I built a pseudo-object-oriented version, >with a bunch of custom ActiveX controls. It went together in a hurry and >worked well, but I had to abandon it when given the req't to port to >Linux. So, now I'm working with RB, with true OE capability, and I end up >with one large object. ;-) No, one large *canvas*. You can still have (and I would recommend) an object for each visual part thereof. Best, - Joe -- Joseph J. Strout [EMAIL PROTECTED] _______________________________________________ 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> _______________________________________________ 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>
