Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » Developing U++ » U++ Developers corner » Should we double-buffer by default?
Re: Should we double-buffer by default? [message #4067 is a reply to message #4066] Wed, 19 July 2006 11:01 Go to previous messageGo to previous message
mirek is currently offline  mirek
Messages: 14261
Registered: November 2005
Ultimate Member
OK, I have tested on my SisGX/Sempron1.8 notebook and while the difference is small, I must say there is difference...

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).

I will test these new ideas tommorow or on Friday.

As for GridCtrl scrolling problem, I think I know where to look and I think it is in CtrlDraw.cpp Smile, but sample code would help, if possible..... (upload to ftp, please).

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


Current Time: Mon Jun 09 01:45:58 CEST 2025

Total time taken to generate the page: 0.04165 seconds