Hi! Yes, you are in for some surprises with anything non-Palm :-( Here's one problem I had with a Visor Prism:
// Acquire handle to draw window deviceDrawWindowH = WinGetDrawWindow(); deviceDrawWindowPtr = BmpGetBits(WinGetBitmap(deviceDrawWindowH)); I use this piece of code to obtain a ptr to the screens bitmap buffer in order to copy directly to screen memory. This works perfect on Palm devices, but returned an invalid memory address on the Visor. You should also be aware that some devices put unexpected control characters in the event queue (e.g. Sony Jog dial events). I also had some problems with broken implementations of WinScreenLock (on a HandEra 330), or WinScreenLock not available on OS 3.5 devices, due to insufficient VRAM. Cheers, Tilo P.S.: I am sure this list is by no means complete. I am also interested to learn more about device peculiarities. P.P.S.: You can find work arounds for the above mentioned display problems in the Razor framework (http://www.tilo-christ.de/razor) in the files DirectCopyCanvas.cpp and PageFlipCanvas.cpp. Look at how CanvasFactory.cpp uses the isSupported method of these classes in order to figure out appropriate display copy routines for the device it runs on. Johnathan Smith schrieb: > I would like to hear from other developers about this > issue. I have a number of products that work great on > all palms but I am getting and number of emails about > erros with the handspring and also the sonys. For > months I been trying to get the roms for both units > but still did not get them! > > __________________________________________________ > Do You Yahoo!? > Send your FREE holiday greetings online! > http://greetings.yahoo.com > > -- > For information on using the Palm Developer Forums, or to unsubscribe, please see >http://www.palmos.com/dev/tech/support/forums/ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
