Home » U++ Library support » Draw, Display, Images, Bitmaps, Icons » flicker
flicker [message #4913] |
Fri, 25 August 2006 00:07  |
jadeite
Messages: 42 Registered: January 2006
|
Member |
|
|
Hello,
Upp 608-dev
iMac Intel core-duo, 2GB ram, 150 GB hard drive for WinXP
In the Drawing package example app, I get alot of flickering of the text "Drawing" and the grey lines when resizing the app. Do others see flickering in this example?
Most apps on this machine scream, so I'm surprised to see the flickering.
Thanks
[Updated on: Fri, 25 August 2006 00:07] Report message to a moderator
|
|
|
|
Re: flicker [message #4939 is a reply to message #4914] |
Sun, 27 August 2006 15:07   |
jadeite
Messages: 42 Registered: January 2006
|
Member |
|
|
luzr wrote on Thu, 24 August 2006 18:19 |
jadeite wrote on Thu, 24 August 2006 18:07 | Hello,
Upp 608-dev
iMac Intel core-duo, 2GB ram, 150 GB hard drive for WinXP
In the Drawing package example app, I get alot of flickering of the text "Drawing" and the grey lines when resizing the app. Do others see flickering in this example?
Most apps on this machine scream, so I'm surprised to see the flickering.
Thanks
|
Actually, see discussion in development threads - this is a long debate. I could avoid flickering forever adding single line to Ctrl constructor, but that would result in lower performance on older machines (including my 6 month old Sempron notebook).
So we are still trying to find the right balance...
Mirek
|
Interesting, you are not double buffering. Now I know why U++ apps feel so responsive and 'light' when resizing. Well, I have to admit that I am surprised that more of your controls, text, etc. do not flicker more than they do. But, basic stuff in that example flickers, so I'm guessing that in most complicated/phat apps, double buffering will be preferred. How do I easily turn on double buffering for the complete app at once? Is it a big performance killer in U++?
[Updated on: Sun, 27 August 2006 15:08] Report message to a moderator
|
|
|
Re: flicker [message #4940 is a reply to message #4939] |
Sun, 27 August 2006 17:38   |
|
jadeite wrote on Sun, 27 August 2006 09:07 |
Interesting, you are not double buffering. Now I know why U++ apps feel so responsive and 'light' when resizing. Well, I have to admit that I am surprised that more of your controls, text, etc. do not flicker more than they do. But, basic stuff in that example flickers, so I'm guessing that in most complicated/phat apps, double buffering will be preferred. How do I easily turn on double buffering for the complete app at once? Is it a big performance killer in U++?
|
Just put BackPaint() in your app constructor. There can be some slowdown but it is only visible if your hardware is old.
|
|
|
Re: flicker [message #4941 is a reply to message #4940] |
Sun, 27 August 2006 19:01   |
jadeite
Messages: 42 Registered: January 2006
|
Member |
|
|
unodgs wrote on Sun, 27 August 2006 11:38 |
jadeite wrote on Sun, 27 August 2006 09:07 |
Interesting, you are not double buffering. Now I know why U++ apps feel so responsive and 'light' when resizing. Well, I have to admit that I am surprised that more of your controls, text, etc. do not flicker more than they do. But, basic stuff in that example flickers, so I'm guessing that in most complicated/phat apps, double buffering will be preferred. How do I easily turn on double buffering for the complete app at once? Is it a big performance killer in U++?
|
Just put BackPaint() in your app constructor. There can be some slowdown but it is only visible if your hardware is old.
|
That's better, much less flicker. There is no noticeable performance difference at all on my hardware.
Thanks.
|
|
|
Re: flicker [message #4943 is a reply to message #4940] |
Sun, 27 August 2006 19:41   |
 |
mirek
Messages: 14257 Registered: November 2005
|
Ultimate Member |
|
|
unodgs wrote on Sun, 27 August 2006 11:38 |
jadeite wrote on Sun, 27 August 2006 09:07 |
Interesting, you are not double buffering. Now I know why U++ apps feel so responsive and 'light' when resizing. Well, I have to admit that I am surprised that more of your controls, text, etc. do not flicker more than they do. But, basic stuff in that example flickers, so I'm guessing that in most complicated/phat apps, double buffering will be preferred. How do I easily turn on double buffering for the complete app at once? Is it a big performance killer in U++?
|
Just put BackPaint() in your app constructor. There can be some slowdown but it is only visible if your hardware is old.
|
Well, to be more correct, call it for all of your main windows...
In fact, I think that we should backpaint much more than we do now, virtually all of "small" Ctrls. Maybe the BackPaint (or better Transparent, which implies BackPaint) could be default...
Mirek
|
|
|
|
Re: flicker [message #12710 is a reply to message #4913] |
Tue, 13 November 2007 17:52   |
nixnixnix
Messages: 415 Registered: February 2007 Location: Kelowna, British Columbia
|
Senior Member |
|
|
Hi there,
I get a lot of flicker and I find that BackPaint() doesnt appear to make any difference.
I do all my drawing to an ImageBuffer which is the same size as my main window. I then use DrawImage to put this on the screen. I also have a DrawGrid function which draws directly to the screen but even with this turned off, I get a lot of flicker. With it switched on I get noticeable tearing as I drag the window contents with the mouse.
I have BackPaint() in my TopWindow constructor.
EDIT: I have also tried adding BackPaint from my InsetFrame and from my SplitterFrame although that is not allowed. Nothing works.
Any ideas please?
Nick
[Updated on: Tue, 13 November 2007 22:16] Report message to a moderator
|
|
|
|
|
|
Re: flicker [message #13035 is a reply to message #12995] |
Thu, 06 December 2007 17:25  |
nixnixnix
Messages: 415 Registered: February 2007 Location: Kelowna, British Columbia
|
Senior Member |
|
|
Thanks Mirek,
I feel a little stupid - the problem was that I was painting the screen white in MouseMove(). Now its fine with or without BackPaint() - doh!
|
|
|
Goto Forum:
Current Time: Sun May 11 22:27:40 CEST 2025
Total time taken to generate the page: 0.01238 seconds
|