>(I'm not just talking to you, Daniel, but to all folks doing stuff like
>this. Things are going to be exciting and different in the months and
>years ahead, so hang on to your hat...)
How about notifying registered developers of these products a little more
than 48hrs in advance? It would be nice to be able to release updated apps
for our customers to run on these new and exciting devices in a timely
fashion.
-----Original Message-----
From: David Fedor <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Thursday, June 17, 1999 12:54 PM
Subject: Re: reading the pen in the grafitti area
>> EvtGetPenBtnList. The array it returns holds the information
>>of the Apps, Menu, Calc and Find silk screen buttons, in that
>>order. (I don't know if that changes on a Japanese device.) I
>>tried it once in a hack and it turned out that it cost more than
>>just using the physical area define's out of hardware.h.
>
>Of course calling an API is slower than hard-coding the area in your app -
>but it seems you've completely missed the point that the buttons can move,
>and have done so already!
>
>Your app might not work properly on a Japanese device, and will also have
>problems on future devices which might have more/different/moved silkscreen
>buttons. Cache the relevant info if you need to get more speed.
>
>Use the APIs, or be doomed to embarassment and annoyed users when a future
>device comes out and exposes your assumptions. Up until now, Palm
>Computing platform devices have been fairly similar to each other, but
>that's not going to stay the case...
>
>(I'm not just talking to you, Daniel, but to all folks doing stuff like
>this. Things are going to be exciting and different in the months and
>years ahead, so hang on to your hat...)
>
>-David Fedor
>Palm Developer Support
>
>
>
