Recent Entries: |
|
|
|
|
|
|
PalmOS Insider Blogs
|
I've had these posted on my links section for a while now, but I realize that it's easy to miss them. Anyway, if you are a PalmOS developer, you need to frequent these two blogs: Ben Combee's PalmOS Blog David Fedor's PalmOS Blog David has been the PalmOS evangelist forever, and he's always giving sneak peeks of cool stuff. As for Ben, before he started working for PalmSource, he was the tech lead for the PalmOS version of the Metrowerks compiler, so he knows all kinds of tricks to make Codewarrior do what you need it to do. Both of their blogs are updated fairly frequently with all kinds of programming goodies. Make sure to check them out.
|
Submitted by bosshogg on Wednesday the 30th of June 2004, at 11:18 am
|
Archiving Feature Added To Hazelware
|
In my lame attempt to copy (read: steal) blog functionality ideas from other people, I have implemented a rudimentary archiving functionality. You can see it on the right. At this point I am not sure if this is exactly the way I want it to function, but for now it will do.
|
Submitted by bosshogg on Wednesday the 23rd of June 2004, at 11:35 am
|
Handheld Programming Tip #3
|
This one is more of a debugging gem, than anything, and it is broken into two parts: Part 1: When debugging on the Treo 600, you MUST use a serial cable. You cannot use a USB cable. That might seem trivial, but if you do not know about it, then you can spend hours trying to get your debugger to connect. Part 2: When the Treo 600 gets a fatal alert, it will automatically reset, and you do not get a chance to see the alert. This is pretty handy for users but can be a pain when debugging. To check out the text of the fatal alert after the reset, go to the phone screen and dial ##377 on the CDMA phones and #*377 on the GSM phones. The text of the last fatal alert will be displayed for you.
|
Submitted by bosshogg on Wednesday the 23rd of June 2004, at 10:05 am
|
Handheld Programming Tip #2
|
It seems like a common topic on the Palm Developer Forums is how to detect if your application is running on the emulator. I am always amazed at how many people do not know how to do this, especially when it is exactly one line of code: bool emulatorPresent = (FtrGet(kPalmOSEmulatorFeatureCreator,kPalmOSEmulatorFeatureNumber,&value) != ftrErrNoSuchFeature);
|
Submitted by bosshogg on Wednesday the 16th of June 2004, at 02:09 am
|
|
 
|
|