Thanks Bob. I thought I'd pass along my appreciation for
your support to all of us on the mailing list for your
help. Honestly, I usually don't read many responses to
questions except from a few people I recognize. Your on
the top of the list.
Thanks,
-- Paul
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> m]On Behalf Of Bob
> Ebert
> Sent: Friday, April 21, 2000 2:00 PM
> To: Palm Developer Forum
> Cc: Palm Developer Forum
> Subject: Re: Graphic Buttons and Backward Compatibility
>
>
> At 3:41 PM +0200 21-04-00, Paul A. Dugas wrote:
> >Any ideas on how I might have a single version of my
> >application that uses graphic buttons while maintaining
> >backward compatibility with 2.0 and 3.x devices?
>
> You could just use the "old style" graphic
> button approach. Empty text and
> draw your own images.
>
> >What will
> >a pre-3.5 ROM do when it sees graphic button resources?
>
> It will attempt to display the bitmap IDs as
> text. This will typically
> either cause funny boxes to be drawn, or will crash.
>
> >Might I have both a 1bpp form bitmap and blank
> button (for
> >old devices) and a 3.5 graphic button occupying the same
> >space on the screen, have them all unusable by
> default, and
> >enable the appropriate ones when the form is loaded?
>
> I think that should work. The only danger might
> be that the old form
> loading routines attempt to munge the text
> pointers, and these could trash
> the bitmap IDs for the graphic buttons. ...but
> of course since you're not
> using the graphic buttons on the old devices,
> you don't really care if the
> IDs get screwed up.
>
> --Bob
>
>
>
> --
> For information on using the Palm Developer
> Forums, or to unsubscribe, please see
> http://www.palm.com/devzone/mailinglists.html
>
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
