> Not an answer to your question, but why use the HR functions on OS 5? > > I use the Palm OS stuff on OS 5 and only use HR if OS < 5 && isSony.
Hey! You're right! Thanks a lot.
Now. Why I didn't use OS5 routines, but Sony's instead? Because my OS5 doubledensity detection procedure failed on the SonyBuild_2002102501 5.0.0.23 Simulator. The function was following:
Boolean DD_Available_Active (void) { UInt32 attr; if (OS_Version ()<0x05003000) return false; WinScreenGetAttribute (winScreenDensity, &attr); return (attr==kDensityDouble); }
and the problem is that the Simulator reports 0x05000000 instead of at least 0x05003000. Indeed, the landscape Simulator shows the right (>=0x05003000) version, and hopefully all real Sony OS5 devices also do.
That is the wrong way to detect double density. As the Palm OS SDK Reference suggests, rather than checking OS version, you should be checking for the presence of the high-density feature set by looking at the version number of the Window Manager. Refer to Appendix A, "High-Density Display Feature Set" for code showing you how to do this.
Remember that high-density isn't just an OS 5 thing. The Palm Tungsten W has a high-density display and supports those APIs, but it's running Palm OS 4.1.2.
--
Ben Combee <[EMAIL PROTECTED]>
CodeWarrior for Palm OS technical lead
Palm OS programming help @ www.palmoswerks.com
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
