Supporting multiple OS versions is always a pain, sigh... My (and this is just me speaking, not Palm) standard trick is to get the OS version on application launch and store it in a global. Then code that is OS version dependent is wrapped in if clauses. If this results in all direct OS structure references only happening on PRE OS 5.0 devices, you should be ok.
I also thought a bit more about your report of a compiler error, not a complaint by POSEr. This indicates to me that you have an EMULATION_LEVEL precompiler variable set. Palm OS uses these variables (as well as other tricks) to produce things like the debug ROMs. They are not needed for third party application programs and in particular should not be defined for third party release builds (I can envision someone finding a use for them for internal debug builds, I suppose). -bob mckenzie, palmsource pdx -----Original Message----- From: Louis [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 06, 2002 12:10 AM To: Palm Developer Forum Subject: Re: Table problem (compiler error) Mmmm interesting. I was using the 3.5 documentation and this function does not exist there. The 4.0 docs do. I am running OS version 3.5.2. Does this mean that I cannot use this function? Thanks for the reply BTW... Robert McKenzie <[EMAIL PROTECTED]> wrote in message news:75794@palm-dev-forum... > > You are directly accessing a system internal (pt->items). This is a big > naughty. I guarantee you that if you do this your code will not run on the > next Palm OS. Please use the published APIs. In particular use: > > Int16 ColumnCount = TblGetNumberofColumns(pT); > -- 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/
