On Aug 04, 2006, at 17:37 UTC, Chris Wysoglad wrote: > A old client called and wants to make revisions to a project we built > back in 2002. After loading the code in and massaging it to get it > compile in 2006r3, we've made our revisions. The problem we're > having now is that there are graphic (canvas.backdrop) changes and > canvas.visible=True/False states across the whole interface. When > it's compiled for Windows, we're running into the flickering/flashing > problems with the refreshes.
I assume this was the case with the old app, too -- Windows has never done double-buffering, so if you erase and redraw (or hide and show) canvases, they're going to flicker on Windows (and classic MacOS), period. > I have tried various other options for > drawing the changes, double buffering the graphics, > erasebackround=false states and nothing is working. Double-buffering works fine when done properly. In a complex app, it can sometimes be a bit tricky to get right though. I'd guess that this is where you need to push a little harder. > I have used the > new code in small, independent apps just to check that I had the > programming right for the refreshes and they worked 100%. But when I > move that code into the main app (4 years old), they still flash. Right, so there is more going on in the main app then you have realized. > I have hit a dead end. Well, don't give up -- it can work. Have you taken out all "Refresh" calls entirely? That's generally the best approach if you want to get rid of flicker. Just draw directly to the canvas.graphics instead. > My boss has asked if anyone has any suggestions on consulting > services to go over the code to find anything. The fact that I can > build alternate "Proof of function" apps independently that are 100%, > and then do not work within the old app tells me that there's just > something with using the 4 year old code that the compiler doesn't > like. No, that cannot be. The compiler has no idea how old the code is. Bits are bits; they don't age. The difference is that your big complex app is doing something more that your simple test apps aren't doing; you need to track that down and fix it. HTH, - Joe -- Joe Strout -- [EMAIL PROTECTED] Verified Express, LLC "Making the Internet a Better Place" http://www.verex.com/ _______________________________________________ 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>
