|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
Our product maintains its own bitmap of everything that appears to the screen. Therefore the only functionality we need is to associate our bitmap with a screen, and have it update rectangles of that bitmap.
Currently we're doing this with (roughly)
that is, there's an HiView control embedded in the main window, and we use that for the bitmap.
All that works great. There's one problem: we deal with pixels and must have the pixels of the screen "line up" with our bitmap. We don't want any scaling.
After creating the window, I size it depending on the bitmap size we're working with: it changes with each CreateWindow call we make.
If I give it a w/h of 400/400, the size of the HiView control is exactly 400/380: the height of the HiView is exactly 20 pixels smaller than the height of the containing ContentRgn window.
If I add 20 to the height of the original SetWindowBounds call, I get what I want, but this is surely not a good way to approach this.
I could use some advice.
It seems like I could code it all without using the HiView, but there's so much there I rely on, including all the input events. And I also like the xxxNeedsDisplayxxx() interface, which makes our coding much simpler.
Any help is appreciated.
_______________________________________________ Do not post admin requests to the list. They will be ignored. Carbon-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
Visit the Apple Store online or at retail locations.
Copyright © 2011 Apple Inc. All rights reserved.