Home
About
Download
Register
Instructions
Other


 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 


 
 Support
Cesium™ is written by one person. Me. Not Microsoft, not RedHat. Me. I will support registered users to the best of my ability. If you are not comfortable with that idea, please use one of the other fine timer / stopwatch programs available for the Palm Computing® platform.

If you send me e-mail about a bug, I'll try to fix it. Understand, however, that this C thing is new to me and I'm learning as I go, so prepare to wait a long time for a fix. I make improvements when I feel like it, usually when my overwhelming sense of ennui is at a low ebb.

Having said that, most registered folk will tell you that I'm quite diligent about replying to my e-mail and attending to bugs.

 Bugs / Technical Issues
Stopwatch Accuracy & Auto Off Disabled.

In Cesium v1.8, the Stopwatch now continues to time even when your Palm Computing device shuts off.  Previous versions of Cesium™ did not allow the Stopwatch to continue timing if your Palm Computing device shut off.

If your Palm Computing device shuts off while the stopwatch is running, or if you leave Cesium to another application during timing, timing accuracy will be reduced to 1 second instead of 1/100th of a second.

If you want to time a long event while maintaining 1/100th second precision, check the Auto Off Disabled box on the Preferences box or find a utility like FPSUtil and set your Palm Computing device so that it doesn't turn off. Also, do not leave Cesium while timing.  Please note that this can be very hard on your batteries. 

A Special Note To Users of EcoHack, Clockmaster & Afterburner...

Overclocking your Palm Computing® device with Clockmaster may cause unpredictable results with Cesium™.  If you must overclock your Pilot, please be sure to exempt Cesium™ from overclocking.  The author of EcoHack assures me that Cesium™ and EcoHack will co-exist, as long as you exempt Cesium™ from overclocking.

Deficiencies, Anomalies, Random Weirdness

Alarms on the Palm V

Some Palm V users have had trouble getting alarms to sound.  This behavior has nothing to do with Cesium.

If you experience trouble with alarms sounding on your Palm V, please try the following:

  • Perform a simple reset on your device.  Then test the alarms.
  • Install the OS 3.1.1 update from Palm.  This update prevents alarms from being cancelled if the scroll up button is accidentally pressed when an alarm sounds.
  • Try setting an alarm in the Palm Datebook application.
  • Make sure that the case you are using isn't pressing on the scroll up key of the V.  It takes very little weight to depress that key, and if the alarm sounds while the key is pressed, the alarm will be cut short.  Be sure you have the OS 3.1.1 update installed.
  • Make sure that you still have native alarm sounds.  From the Palm Datebook application, choose Menu|Options|Preferences.  Make sure that there is a sound displayed to the right of the Alarm Sound: label.  If you see a black bar with no text, please contact Palm Support.
Other Issues...
  • Please be sure that you are running the latest OS update from Palm. There have been anecdotal reports of discrepancies between the time an alarm was set and the time that the alarm actually went off.  It would appear that this is a bug in the Palm OS and not something that I am able to fix.  The OS 2.0.5 and 3.0.2 updates from 3Com should fix this problem.  Besides, you should install these fixes anyway.  Your Palm Computing device will thank you for it.  If you have installed the OS updates and you still see discrepancies in the time you set the alarm for and the time it went off, I encourage you to send me e-mail as well as Palm/3Com.
  • If your Palm device goes to sleep while the Timer is running, you may experience a delay of up to 60 seconds after the Timer expires before the Timer alarm goes off.  Again, this is a feature of the Palm hardware and not a deficiency in Cesium™.  The Palm device checks if an alarm has expired at the top of each minute.  If the device checks for an alarm and then the Timer expires a second later, the device won't realize that an alarm has expired until the next check, 59 seconds later.  This bug should not affect the Clock alarm since the clock alarm is always set to expire at 0 seconds, allowing the device to catch the alarm.
Known Bugs
  • 1.8.1 - If the System alarm is selected in Cesium | Preferences | Alarm | System, the alarm will ring one more time than the number of rings displayed.  For example, setting the number of rings to X 2 would give you three rings.  To be corrected in the next release.
  • 1.8 displayed the wrong week of the year (last minute change by the programmer...bad programmer, bad...<swat>, <swat>...).  Fixed in 1.8.1.
View Cesium™' Revision History
Home   Top
Send e-mail to the author
Copyright ©1997, 1998, 1999 Andrew Ball.  All rights reserved.
Last revised June 15, 1999