> For example, how do I tell what a device's actual resolution is, e.g.,
> 480 x 320 vs 320 x 320 vs 450 x 320 vs 320 x 480, etc.? For full screen
> Apps there is more to the concept of full screen than telling a DIA to
> open or close. I still can't determine if the Tungsten T3 actually CAN
> run a 480 x 320 App, and there are no examples out there to indicate it
> can. So what do I tell customers?
// get the current display information
WinScreenGetAttribute(winScreenWidth, &gDALGlobals->gfx.width);
WinScreenGetAttribute(winScreenHeight, &gDALGlobals->gfx.height);
i wish those worked as they should. they used to in the 'early' T3
roms that existed, then, all of a sudden, they ended up returning
320 and 320 for the width and height.
as such, my code started to break :( i had to end up checking for the API :(
// hawkeye device?
deviceP->palmHDD.hawkeye.device =
(FtrGet(statLibCreator, statFtrNumVersion, &version) != ftrErrNoSuchFeature);
not the way i want to do things. this is very bad. many many many
months ago i proposed a set of features developers could access to
get the display information.. this included:
- direct access to display controller registers
- *real* width/height values
- *real* screen pointer access
sure, we could abuse them; but, its better than having to do a
bunch of checks like we do to get it working the way we want..
its starting to drive me nutz as well - you are not the only one.
---
Aaron Ardiri
[EMAIL PROTECTED]
http://www.mobilewizardry.com/members/aaron_ardiri.php [profile]
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
