For my programs, I created an abstraction layer. For example, say you want to draw a color line. I've wrapped the device-specific line drawing routines in my own routine (MyWinPaintLine). If the device supports color, WinPaintLine is called. If not, WinDrawLine is called. It's a little more complex than that, but I'm sure you get the idea.
Nigel Grant wrote: > Hi Guys > > I was wondering if any of you have come up with a smart way of > handling options for the various devices. > > I current have a case statement that performs different processing for > the various devices. > > Pseudo code > > Case PalmV > . > . > . > break > > Case PalmVx > . > . > . > break > > Case M505 > . > . > . > break > > Case T600 > . > . > . > break > > Case T650 > . > . > . > break > > etc. etc. etc. > > I can see this case statement becoming hugh as I test for more and > more of the different devices. > > Any Ideas ? > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
