As far as I'm aware they do. Without staring at the code in huge
detail I'd base that off of the observation that it works on Leopard
just fine (the Tiger box is also an Intel box, just like the 10.5
machine).
I would have thought that if it were an ordering issue I'd see the
same incorrect values on both system versions.
They are certainly not far enough askew to be thinking that it's
something like interpreting ARGB as BGRA for example.
I've put links to two sample videos. One for leopard and the same code
running on Tiger.
The original RGB values of the blue of a highlited row in a table
is 56,117,215. After grabbing and turning into a CIImage via a
CGBitmapContext, that turns into 116,179,239. Once it's
composited back onto the original frame it has become 170,217,250.
I feel I'm missing something quite basic here... can't for the
life of me spot it at the moment.
Any tips/suggestions that I might try?
Do all the parties agree on the byte order of the pixels?
-Marc
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartz-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartz-dev/email@hidden
