Has anyone had this problem with XP?

[joey o.]

Hi

I've got some code that works on Win98 but not on XP. I'm making an "on-the-fly" mask maker.
I do some inversions and use myPic.point (1,1) to assign the current transparent color to use within a Transblit (I'm sure transblit is working fine)function. The machine has loads of memory yet it seems like its spliting colors up like it's in 16 bit or something. So when I pick any given point it may not contain the true color but a representation of it. I believe this is the problem as my code works when I use constants in my code instead of depending on point. I don't have access to the xp machine more than once a week so if any one knows?

My question: Is there a way to find out the backcolor assigned to a window even if XP thinks it knows a better way to display it?

My Other question: Has anyone else had this problem with XP?

[Fox]

I heard of masking problems when using BitBlt - there seems to be a weird swap of black and white in older windows versions. Didn't hear of your problem yet thought..

[joey o.]

Do u have more info on the swap problem Fox? It may have to do with the way "any" color is interpreted seeing that masking is 2 inverted colors added to negate each other (at leat that's how I understand it) and I'm making the masks with an interactive backcolor to consistently keep the backcolor transparent.

[Fox]

Hm no I just figured out I have to use white instead of black when running programs on older windows.. That was when blitting using vbSrcPaint and vbSrcAnd, I never use color masks.