EvtGetPenBtnList acts like it succeeds but returns all (0,0,0,0) rects for the soft button locations. This is why the user can't press launcher or menu.
EvtGetSilkscreenAreaList returns three regions that are plausible, albeit in low res coordinates, but nothing about the lower control bar.
=========================================================
Time to write an *OPEN LETTER TO PALM SOURCE AND PALM ONE*
1) If a device doesn't support official OS calls, it should not be able to get the PalmOS logo.
2) If certain calls are going to be officially removed from the PalmOS, this should be CLEARLY stated along with a suggestion of a new function to replace them. Do not assume that we are always rewriting all of our old, working code to just for the sake of saying we're using the latest and greatest APIs.
I get so mad about this, because I can just see some Palm designer somewhere saying "hmmm... nobody uses this function.. we'll just silently stop implementing it..." And then we find out because the Palms are selling off store shelves and customers are asking us why our app doesn't work.
THE MOST BASIC FUNCTIONS for the PalmOS shift like sand!
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?
This kind of stuff is extremely frustrating. At least each licensee provides an actual SDK path and actual sample code for basic functions.
So I will complete this rant with some final points:
1) We get very little value from the "PalmOS" as a concept because we have to write new code for every single device. In our minds, the purpose of an operating system is to allow code to run on other devices with the same OS. If we ever stop updating our app, it will stop working on most future Palm devices. It is getting to the point where it is barely economical for us to stay in the PalmOS platform.
2) Palm keeps all of its API decisions much too secret from developers, and gives them access to new simulators much too late given point (1). I'm guessing that Palm has a Simulator for a device as part of designing and testing that device, and they need to make it available earlier. We all sign NDAs here.
THERE IS STILL TIME TO CHANGE FOR THE BETTER...
For example, I'm getting an inkling from forum news that Palm is weakening support for the old database format and functions in the upcoming APIs - which would entail unimaginable amounts of development for us to adapt. So if this is true, do we get to know about this with a year's lead time or after the devices go on sale?
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
