At 10:18 PM 3/29/2007, you wrote:

>You are working on a Windows application, so you will have Windows related
>problems, and so, maybe, you need to step out of your bounds and try a
>different approach.
>
>NOTE: Double-buffering can be applied to any computer platform that draws
>graphics.  The only difference is that Macintosh uses built-in
>double-buffering.  As for Windows, you create your own double-buffer in
>code.  It is very easy to do and the code in the LR shows you at least part
>of the steps to do this in RB.  The concept is to place a complete image in
>memory before displaying it.  Then, display it on a surface instead of using
>resources to both draw and create the image.  Believe me, this relates to
>Windows.  IF you do not do this, any graphic you have that need updating
>will be very flickery.  See "flicker" below.

>If you continue having these issue, feel free to create a simple example
>that has these specific problems and send it to me off list.  I'd be happy
>to take a look at it and see if I can help in any way.

Thanks very much for your excellent reply. I'll do just that.

What I found was that on the Mac I was using BackDrop, and that was 
effective. Windows - lots of flicker - so I removed the
"Canvas.Backdrop = [picturefile]" statements and put this into that 
Canvas controls Paint event:

P = [picturefile]
[maybe put in a mask]
Canvas.DrawPicture(P, 0, 0)

Going back to the Mac, I found the Paint event solution entirely 
failed, so I #ifdef'd the backdrop and Paint things. It looks like 
Backdrop does NOT do the same thing as the Paint thing. Why I don't know.

To be specific, the application I am creating will be on display at 
NAB - the National Association of Broadcasters in Las Vegas in couple 
weeks. It was decided (grrr) that it would be displayed on 3 
different PC workstations, not Mac's. My manager is peeved about the 
flicker, so time to step on the programmer (me) to achieve the 
results at all costs. =)

The program uses semi-small Canvas controls that display Audio 
waveforms ("clips") and are meant to be dragged around an interface.

Right now I've isolated the flicker into 3 areas - 1) a 
quick-updating time counter in a StaticText that sits on a Canvas, 2) 
white flashes when a Clip is visible and invisible, and 3) quivering 
Clips when picture has to be updated frequently (100ms or so) to 
display a moving Progress line and a "smoky mask" that shows where 
the Progress line has travelled.

I find the problem 1) to be the most daunting. I will dissemble 
things and see what I can do and forgive me if I could consult you 
again (I'll owe you!)

I do understand (and relayed as much to my manager (who is 
Zero-Windows literate)) that Windows is a more flickery platform and 
certain things won't go away. But that isn't satisfying him at the moment.

* * * * * * * * * * * * * * * * * * * * * * * * * * *
| Garth Hjelte                                      |
| Customer Service Representative, President        |
| Chicken Systems, Inc, Rubber Chicken Software Co. |
| 714 5th Street SE                                 |
| Willmar, MN 56201 USA                             |
|                                                   |
| 800-8-PRO-EPS    Toll Free Order Line (US Only)   |
| 320-235-9798     Tech Support, Sampler Questions  |
|                  International Line               |
| 360-838-7689     Fax                              |
| Product Sales:   [EMAIL PROTECTED]             |
| Product Support: [EMAIL PROTECTED]           |
| Sampler Q+A:     [EMAIL PROTECTED]                |
| Web Page:        www.chickensys.com               |
* * * * * * * * * * * * * * * * * * * * * * * * * * *

_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>

Reply via email to