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 » U++ Library support » Look and Chameleon Technology » Appearance problem in TabCtrl
Re: Appearance problem in TabCtrl [message #32550 is a reply to message #32549] Tue, 24 May 2011 17:37 Go to previous messageGo to previous message
mirek is currently offline  mirek
Messages: 13976
Registered: November 2005
Ultimate Member
qapko wrote on Tue, 24 May 2011 10:25

Hello,
I have appearance problem in TabCtrl on one machine running Windows XP using Ultimate++ 3211. Problem appears after setting transparent (opaque)



Is not transparent oposite of opaque?!

Quote:


	if(GetKind() == IMAGE_OPAQUE && paintcount == 0 && sr == Rect(sz) && IsWinNT() && w.IsGui()) {
		LTIMING("Image Opaque direct set");
		SetSurface(w, x, y, sz.cx, sz.cy, buffer);
//		paintcount++;  /* removing this line helped */
		return;
	}




Well, this piece of code is sort of optimization - if particular Image is painted only once, it is not transfered to BITMAP and painted directly ('SetSurface'). If painted for the second time, it gets coverted to BITMAP and painted that way, as we supposed that BITMAP is faster for repeated paints.

By removing the line, you force U++ to paint it always directly.

So, the first estimate is that Image is misclassified. Where is Image coming from? Is it .iml file, or is it something synthetised?

All in all, testcase would be fine...

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
Previous Topic: BUG? ImageOp's not HotSpot aware
Next Topic: Font drawing in linux
Goto Forum:
  


Current Time: Sat May 11 20:49:25 CEST 2024

Total time taken to generate the page: 0.02995 seconds