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 #4060 is a reply to message #4058] Wed, 19 July 2006 00:42 Go to previous messageGo to previous message
mirek is currently offline  mirek
Messages: 14261
Registered: November 2005
Ultimate Member
Reply to ICQ:

> Mirek I don't understand. If theide is now all double-buffered why I can see eg in thisbacks window when scrolling array that first body of array ctrl is scrolled and then child controls

- because scroll is used to scroll window area. Double buffering takes effect later... (yes, I still have "detect Ctrl position change that is scrolled and avoid repainting" in my list. When that will be done, this will disappear).

- also, sometimes (e.g. HeaderCtrl) there is Sync that forces immediate repaint

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: Sun Jun 08 22:21:46 CEST 2025

Total time taken to generate the page: 0.04337 seconds