While I wait for the simulator to re-start after yet another crash - I feel a rant coming on.
Things that driv e me mad with the Simulator ( under Code Warrior) :- It crashes far too easily and far too often and when it does it either bombs out completely taking the Code Warrior IDE with it or wants to drop into the Window's debugger rather than the Palm Debugger - thats helpful!!!. Most of the time it wont let you set breakpoints on the fly. You have to re-start it and set fixed breakpoints. What sort of use for debugging is that? More often than not when you try to re-start a debugging session - the debugger cant connect to it - and you end up having to tear the simulator down and start again. (and you more often than not have to check that there isnt a zombied PalmSim process still running away with your CPU somewhere). I have found deleting the app from the simulator before trying to re-run the debugger can prevent this hang up sometimes. If only we could find a way of charging PalmSource a tax for all the time being lost during development when using their Simulator. Then when we've collected enough from them - pay someone to make a POSE again. The emulator was so good - you dont know what you've got till its gone!!! -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
