> -----Original Message-----
> From: Vinay Vinay
>
> Hi ,
> I have two problems with code warrior IDE one is with code
> warrior 7.
>
> 1. With Code Warrior 6 -
> After debugging application , when I am trying to run the
> application it
> is now allowing to run or to debug the application second
> time. For that I
> have to colse the IDE and I have to open it again to run the
> application.
> How to avoid this.
>
Vinay,
Make sure that you completely end one debug session before
attempting to debug a second time by hitting the Kill button
(the red 'X') in the debugger window.
There are updated debugger plugins for CW for Palm 6 that are
available for download from our web site, so you should install
these as well.
You might also want to try deleting the debugger cache files,
which are located in the Windows\Metrowerks folder (on Mac, it
should be in the system folder). There should be a CW debugging
cache and/or CW autosave folder. Exit the IDE and delete the
contents of both of these folders.
> 1. With Code warrior 7-
> Is it possible to develop the application for Palm OS 3.0,
> I am not able
> to compile the code wich is from code warrior6. Because CW6
> uses Pilot.h and
> CW7 uses PalmOs.h.
Yes, it is possible but you should be able to do anything under Palm
OS 3.5 that you did under Palm OS 3.0. The reason for the errors is
due to the numerous changes Palm made to the SDK from 3.0 to 3.5 and
above including changing Pilot.h to PalmOS.h.
To convert your project to the newer SDK, you will
need to do at least these three things:
1. Change your access path to look for the 3.5 Support folder.
2. Change all the places where you have #include <Pilot.h> to #include
<PalmOS.h>. The API changed pretty significantly, so Pilot.h doesn't
exist anymore.
3. Add a #include <PalmCompatibility.h> line in all your source files
right after you include PalmOS.h to handle all the typedef
incompatibilities.
You may also have to correct non-ANSI-compliant code, as the compiler
in version 7 is stricter than the one in earlier releases.
For more information on converting projects from older SDKs, please refer to the
following article from the developer knowledge base:
http://oasis.palm.com/dev/kb/papers/1710.cfm.
The other option is to continue using Palm OS 3.0 by changing the access
path in the CW for Palm 7 project to point from the Palm OS 3.5 Support
folder to Palm OS 3.0 Support.
Vinu
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/