U++ forum: Welcome to the forum

Status & Roadmap

Authors & License

Funding Ultimate++

Search on this site

Search in forums

Home » Developing U++ » U++ Developers corner » Should we double-buffer by default?

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Return to the default flat view

Create a new topic

Submit Reply

Re: Should we double-buffer by default? [message #4070 is a reply to message #4067]

Wed, 19 July 2006 11:18

unodgs is currently offline

unodgs
Messages: 1367
Registered: November 2005
Location: Poland

Ultimate Contributor

luzr wrote on Wed, 19 July 2006 05:01

OK, I have tested on my SisGX/Sempron1.8 notebook and while the difference is small, I must say there is difference...

Good I'm not alone Wink

Wink

Quote:

Means back to development.... Now I am thinking about some sort of more simple approach to the old problem.... In fact, the real trouble of all this is "sibling Ctrl intersection". That makes all the trouble, if I want really correct algorithm. Anyway, at the same time it is not very often corner case.
So my next idea is to detect this problem and perform non-buffered draw just for ctrls that do not have this problem. Also, maybe we could detect and handle unbuffered just Ctrls that are "big" (say bigger that 200x200 pixels).

Could you describe the problem of sibling ctrl intersections more? (if you have time, I would like to think about solution too Smile

Smile

)
As for unbuffered draw this is some kind of idea. I would also add to this ability to set by hand if control is or isn't double buffered.

Quote:

As for GridCtrl scrolling problem, I think I know where to look and I think it is in CtrlDraw.cpp Smile

Smile

, but sample code would help, if possible..... (upload to ftp, please).

I will upload it today evenig - no problem.

Report message to a moderator

Send a private message to this user

[Message index]

		Should we double-buffer by default? By: mirek on Tue, 18 July 2006 15:23
		Re: Should we double-buffer by default? By: mirek on Tue, 18 July 2006 15:31
		Re: Should we double-buffer by default? By: unodgs on Tue, 18 July 2006 15:56
		Re: Should we double-buffer by default? By: mirek on Tue, 18 July 2006 16:36
		Re: Should we double-buffer by default? By: unodgs on Tue, 18 July 2006 23:43
		Re: Should we double-buffer by default? By: mirek on Tue, 18 July 2006 23:57
		Re: Should we double-buffer by default? By: mirek on Wed, 19 July 2006 00:42
		Re: Should we double-buffer by default? By: unodgs on Wed, 19 July 2006 08:09
		Re: Should we double-buffer by default? By: unodgs on Wed, 19 July 2006 08:34
		Re: Should we double-buffer by default? By: mirek on Wed, 19 July 2006 09:01
		Re: Should we double-buffer by default? By: unodgs on Wed, 19 July 2006 10:09
		Re: Should we double-buffer by default? By: mirek on Wed, 19 July 2006 11:01
		Re: Should we double-buffer by default? By: unodgs on Wed, 19 July 2006 11:18
		Re: Should we double-buffer by default? By: mirek on Wed, 19 July 2006 11:47
		Re: Should we double-buffer by default? By: unodgs on Wed, 19 July 2006 16:25
		Re: Should we double-buffer by default? By: mirek on Wed, 19 July 2006 16:43
		Re: Should we double-buffer by default? By: fudadmin on Wed, 19 July 2006 17:59
		Re: Should we double-buffer by default? By: mirek on Wed, 19 July 2006 18:56
		Re: Should we double-buffer by default? By: fudadmin on Wed, 19 July 2006 19:23
		Re: Should we double-buffer by default? By: mirek on Wed, 19 July 2006 21:14
		Re: Should we double-buffer by default? By: fudadmin on Fri, 21 July 2006 04:52
		Re: Should we double-buffer by default? By: mirek on Fri, 21 July 2006 10:44
		Re: Should we double-buffer by default? By: mirek on Fri, 21 July 2006 12:10
		Re: Should we double-buffer by default? By: fudadmin on Wed, 19 July 2006 19:38
		Re: Should we double-buffer by default? By: mr_ped on Wed, 19 July 2006 15:04

Previous Topic:	let's discuss new Draw principles and problems...
Next Topic:	A list of SQL dialects to support (eventually)..

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

PDF

]

Current Time: Mon Jun 09 00:15:28 CEST 2025

Total time taken to generate the page: 0.03988 seconds