kCoordinatesNative works fine for me. Just for grins, as a test I recompiled my Icon Manager app to use kCoordinatesNative instead of the places it used kCoordinatesDouble (http://www.palmgear.com/software/showsoftware.cfm?prodID=47054). The high density drawing works identically regardless of which I use. I use WinDrawLine and several other APIs in the kCoordinatesNative coordinate system.
It seems likely the problem lies elsewhere, or that there are some details that haven't been presented. "Chris DiPierro" <[EMAIL PROTECTED]> wrote in message news:113202@palm-dev-forum... > > > hmm.. interesting - i have never used an API in 'native' resolution mode > > :) the other option is to create a V3 bitmap offscreen window, draw to > > that, then blit to the screen :) [this is what we do, works fine] > > > > the fact that it stops within the 160x160 boundary would tell me it is > > clipping issues - did you try WinResetClip(); after the call to set > > the co-ordinate system? > > > > thats all i can think of - if not, we got a bug on our hands :) > > Using WinSetClip (&r), where r is a 0,0,320,320 rectangle and then calling a > WinGetClip returns a 0,0,160,160 rectangle back. > > Result is same with WinResetClip() > > I can't believe that this is a bug in OS/5. You're telling me that in all > the time OS/5 has been out that no one has drawn past 160,160 natively? I > can't really believe that.... > > > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
