OK. I did try putting the code in the Constructor, but I put it after the Super.Constructor call. I'll try again.
I was sticking to RB5.5.5 rather than upgrading, because I got the impression, from reading various posts, that newer versions are slower. For my app, it's critical that the screen updates quickly, although updates don't happen often. Where's the sweetspot, version wise, for that kind of performance? Thanks. Paul At 6:32 PM -0800 3/30/06, Paul Mathews wrote: >However, for the life of me, I cannot figure out where to put the code so >that it gets executed BEFORE the initialization of things like >SpriteSurfaces. You could put it in the window constructor -- I'm pretty sure we had that back in 5.5.5. :) That fires before the open events, which will get called when you invoke Super.Constructor. >A related question: Other Properties are shown in bold in the Window >browser, but my DiePatterns property (above) remains unbolded. What does >this mean? Ah, that means you should upgrade to a newer version of RB, where that bug has been fixed. (Bold is *supposed* to mean that you have some notes attached to the property, but it never worked right prior to RB2005.) 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>
