new CountDown Timer (need opinions) - BlackBerryForums.com : Your Number One BlackBerry Community

obijohn · 07:05 AM

EDIT: updated to version 0.6 (see readme.txt below for changes)

I've written a CountDown Timer app and I'd like input/suggestions on features which should be changed or added. The attached zip includes the readme.txt file and the Desktop-installable files. If you'd like to install OTA, the link is:
http://johnstoneham.com/bb/CountDown.jad

For those installing OTA, I will paste the readme.txt here.

PLEASE NOTE: Time entry is done as a single number, with 2-digit groups automagically parsed into HH MM SS (e.g. 130 is 1 minute 30 second). This is done so that the time can be entered quickly in one text-entry field, without having to change from an hours field to a minutes field to a seconds field (which always bugged me about setting the time on the built-in alarm).

ALSO NOTE: The secondary alerts do not have a "seconds" part (e.g. a value of 2 for a secondary alert means 2 minutes, not 2 seconds).

Anyway, let me know what you think, and I'll be looking forward to your suggestions!

README.TXT

Code:

COUNTDOWN TIMER
----------------

Version 0.6
Copyright (c) 2006 by John Stoneham
captnjameskirk@yahoo.com

***File locations***

  Desktop installable files:
  http://johnstoneham.com/bb/timer.zip
    -contains this readme file, countdown.alx, countdown.cod, 
     countdown.jad and countdown.jar
    
  OTA location:
  http://johnstoneham.com/bb/CountDown.jad
  
  Current version readme:
  http://johnstoneham.com/bb/timer.txt
    
  
***Description***

OS requirements: 4.0 or higher

CountDown Timer is intended to serve one purpose: to be a simple, easy-to-use, 
countdown-style timer with 0-time, secondary, and repeating alerts for 
BlackBerry java-enabled devices. It is NOT intended to be a general purpose 
chronograph or stopwatch with split times and millisecond accuracy.  

TIME ENTRY:  
Most of the settings should be fairly self-explanatory, however I should first 
mention the unique way CountDown Timer displays and reads time values. Time 
values do not contain separators between hours, minutes, and seconds, such as 
":" or "|". Imagine a 4-digit number where the first 2 digits are minutes and 
the last 2 digits are seconds, such as 1230 representing a time of 12 minutes 
30 seconds, and it will be second nature almost immediately.  However, the 
number doesn't have to be 4 digits. If you only enter a 1- or 2-digit number 
it would be in seconds, and a 5- or 6-digit number would be hours, minutes, 
seconds. NOTE: Secondary alerts and repeating alerts DO NOT have a seconds part.
A value of 1 for a secondary alert would be 1 minute, not 1 second, and a value 
of 100 for a secondary alert would be 1 hour, not 1 minute. See below for more
on secondary and repeating alerts.

A couple of examples will make the main time entry clear:
  
  To enter a time of 30 seconds, enter: 30
  To enter a time of 1 minute 0 seconds, enter 100
    -If the number entered exceeds 2 digits, the two least
     significant digits represent seconds. If you enter 60
     to represent 1 minute, it will be converted to 100
     when you click the Start Button.
  To enter a time of 1 minute 30 seconds, enter 130
    -Note that you could also enter 90, which would be
     converted to 130 when you click the Start button. 
     This means it's possible to enter a value such as 190, 
     which would equal 1 minute 90 seconds, or 1 minutes plus
     1 minute 30 seconds, which is 2 minutes 30 seconds. An 
     entry of 190 would be converted to 230 when you click 
     the Start button.
  To enter a time of 10 minutes 0 seconds, enter 1000
  To enter a time of 1 hour 30 minutes, enter 13000
    -If the number entered exceeds 4 digits, the left-most
     digits represent hours: HH MM SS (although the hours part
     can be up to 4 digits, resulting in an 8-digit number).
     Note, as explained above, that you could also enter 9000 
     here, which would be converted to 13000 when you click 
     the Start button.

SHORTCUT KEYS:
Q        - Reset timer
ENTER    - Start/Pause timer
P (O/P)  - Minimize
L        - Elapsed/Remaining toggle
Z        - Zoom timer display
ESC      - Quit/Minimize dialog

START/STOP/PAUSE/RESET:
While counting down, the Start button becomes a Pause button. If you pause a 
countdown, the button becomes a Resume button unless the time entry value has
changed while the countdown was running, in which case the button then becomes 
a Start button again. If you edit the value of the time entry, either while 
the timer is running or paused, this new value becomes the new countdown value 
whenever the Start/Pause button is clicked. This means that you can edit the 
timer entry field while the timer is running, but the new value will not take 
effect until you click the Start/Pause/Resume button, or when you click the 
Reset button. The Reset button, as its name implies, resets the timer to the 
current value of the main timer entry field (which may be a new value). The 
reset will take effect even if the timer is running, allowing for a quick 
restart of a new countdown. Whenever the Start or Reset buttons are clicked, 
the current values of the main timer and secondary alerts are saved and will 
be the default values the next time the app is started. If you've edited a time
value but haven't used it (i.e. you haven't clicked the Start/Pause/Resume or
Reset buttons) that value won't be saved when you exit the app. You must use
a value to save it.

The ENTER key is a shortcut for pressing the Start/Pause/Resume button. This is
mainly useful when entering a value in the Timer entry field or one of the 
alerts. Pressing ENTER in one of the time entry fields has the same effect as 
clicking the Start/Pause/Resume button (that button will then have focus and be 
selected). On some devices, this shortcut will work when outside the time entry 
fields as well, but this behavior is unsupported.

When the total elasped time has expired, the main alert will play if "Tone" is 
checked, and the device will vibrate if "Vibrate" is checked. An alternate tune 
is available, called "Mosquito", which is faster and has a higher pitch than the
standard tune (which is called "Encounters"). The Mosquito tune may be more 
noticeable and easier to hear in loud surroundings. 

If you would like to see the elasped time displayed instead of time remaining, 
select the "Elapsed" checkbox. This acts as a toggle and can be selected while 
a countdown is running. The "L" key is a shortcut for selecting the Elapsed 
checkbox, and is valid anywhere on the screen except for the time entry fields. 
Pressing the "L" key toggles the Elasped checkbox and the countdown display will 
then change between Elapsed Time and Remaining Time.

The "Z" key will zoom the current countdown time (the other screen elements are
not effected). There are 4 zoom levels, and pressing the "Z" key will toggle
between them. NOTE: Zooming is disabled when the time is greater than 100 hours.

MINIMIZE:
There are three ways to minimize the app, which will cause it to continue a 
running countdown in the background. The "P" key (the single "O/P" key on the 
7100/8100) is a shortcut key to minimize, which causes the app to immediately go
to the background. Pressing ESC will bring up a Quit Dialog box, one option of 
which is "Minimize". Also, when the Quit Dialog is open, pressing ESC again will
minimize the app; this means that a quick shortcut to minimize the app is double 
clicking the ESC key. If "Restore" is checked, when the specified time has 
elapsed the timer will become the foreground app again and vibrate and play the 
alert tone if those items are checked. If "Restore" is unchecked, it will remain
in the background but still vibrate and/or play the alert tone if those items 
are checked. NOTE: Secondary alerts will not cause the app to restore, even if 
"Restore" is checked.

SECONDARY ALERTS:
There are 4 additional time entry fields: Alert 1, Alert 2, Repeat Start, and 
Repeat Every. Unlike the main time entry field, these fields DO NOT have a 
"seconds" part (a value of 1 means 1 minute, and a value of 100 means 1 hour).
The Alert fields indicate that a secondary alert will sound when X time remains 
in the countdown. Repeat Start marks a secondary alert as well, and it also sets
a threshhold time at which a repeating alert will begin. The actual value of the 
repeat time is indicated by the Repeat Every field: an alert will sound at every 
X interval, but as counted up from 0. For example, if Repeat Start is 6, and 
Repeat Every is 2, an alert will sound with 6 minutes remaining, 4 minutes 
remaining, and 2 minutes remaining. However, if Repeat Start is 7 and Repeat 
Every is 2, an alert will sound with 7 minutes remaining, but the repeat alert 
will actually begin with 6 minutes remaining (not 5), and repeat again with 4 
minutes and 2 minutes remainining. If Repeat Start is 0 and Repeat Every is NOT 
0, then the repeating alert begins when the countdown itself begins. All these 
values can be edited while a countdown is in progress; however, they will not 
take effect until the current countdown is reset or paused and restarted. If you
try to enter a value that would be out of range (for example, if the main timer 
was set to 10 minutes and you try to enter a value of 30 minutes for an alert), 
it will be reset to 0 when you press the Start/Pause/Resume or Reset buttons to
reflect the fact that the alert would have no effect.
NOTE: Secondary alerts will not vibrate unless *only* Vibrate is checked (i.e., 
Vibrate is checked but Tone is unchecked). In other words, secondary alerts are 
"tone-only" alerts unless the main alert is "vibrate-only". 

***Changelog***

Sept 1, 2006
  First public release, ver 0.1
  -most initial planned features are implemented

Sept 22, 2006
  Release 0.2
  -increased size of Count Down field
  -tweak in default cursor placement in time entry field

Sept 24, 2006
  Release 0.3
  -added Alert and Repeat fields, support for secondary and repeating alerts
  -rearranged layout to accommodate the above features
  -added "P" (O/P) minimize shortcut key 
  -fixed display sync (displayed time was 1 second less than the internal time)
  
  Release 0.4 (same day!)
  -added Restart button
  -added Minimize option in Quit Dialog, and double-ESC shortcut
  -removed Minimize button (it was now redundant)
  -rearranged layout again due to the above changes 
  
Sept 27, 2006
  Release 0.5
  -added an option to display elapsed time
  -added the "Mosquito" tune
  -added "Q" (reset), "ENTER" (start/pause), and "L" (elapsed/remaining) 
   shortcut keys
  -fixed a bug where changes in the secondary and repeating alerts did not take
   effect when the Reset button was clicked before clicking the Start button
  -fixed a bug in which an exception was thrown if the Start button was pressed 
   while one of the time entry fields was completely empty
  -fixed a stupid bug in the "vibrate only" setting

  Release 0.5.1
  -relabeled the "Start Timer"/"Pause Timer" button to "Start"/"Pause" so that 
   there is enough room on the 8100 (Pearl) display for the Elapsed checkbox
   
Sept 28, 2006
  Release 0.5.2
  -usability fixes:
   *enforce maximum allowable time for main time and secondary/repeat times
   *Start/Pause button now indicates "Resume" when a countdown is paused
  -general code cleanup
  -more specific description of time entry and alerts in the docs
  
Oct 23, 2006
  Release 0.6
  -added zooming feature and "z" shortcut key

obijohn · 09-01-2006, 02:01 PM

I forgot to mention that this probably requires OS 4.0 (4.1 is definitely ok). The API docs say that the audio functions I'm using require 4.0 or higher, so I guess that's true. I have tested it on just about every model in the Simulator pack and it appears to work fine on them all, but I only have 1 "real" unit (a 7100t running 4.1).

If you test it and it works on your unit, please post a reply to this thread stating the model you have and your OS version if you know it, so I can keep track of what models it's known to work on.

Thanks everyone!

Dispatcher35 · 09-01-2006, 07:37 PM

Just installed it and tried it on a 7100i with 4.1 and worked like a champ. Only thing is the alert tone could be a little louder.

Mike

obijohn · 09-01-2006, 08:46 PM

Quote:

Originally Posted by Dispatcher35

Just installed it and tried it on a 7100i with 4.1 and worked like a champ. Only thing is the alert tone could be a little louder.

Mike

Thanks, glad it works ok for you! Unfortunately, RIM has not exposed an API that allows apps to play the tones and alerts already stored on the phone; the app has to create it's own, and the options are limited. The alert I'm using (anyone notice what it is?) already is at it's loudest volume, which is one reason I thought that vibrate should be offered in addition to the tone.

dbit · **Thanks -** 09-03-2006, 12:47 PM

This is great for playing cards, (raising the blinds). Works great on my 7130e.

Thanks
D.

rambo47 · **OS:** 4.7.1.57

Very nice little app! I especially like that it's a very small application, eschewing a fancy interface for a no-nonsense countdown timer to save space. Does exactly what it's supposed to do, no more, no less.

obijohn · 09-03-2006, 02:23 PM

Quote:

Originally Posted by rambo47

Very nice little app! I especially like that it's a very small application, eschewing a fancy interface for a no-nonsense countdown timer to save space. Does exactly what it's supposed to do, no more, no less.

Thanks! One of my goals was for it to consume very few resources when "minimized" and running in the background.

patrickh · 09-20-2006, 08:55 PM

Features request:

May be a better time selection field and larger display of the count down.

Also, ability to set alerts before the timer expires.. like if it is a 15min count down, I would like to set multiple alerts at 10, 5, 1 minutes, etc. This would be helpful for chairing time-limited talks, etc.

P

obijohn · 09-22-2006, 03:34 PM

Quote:

Originally Posted by patrickh

Features request:

May be a better time selection field and larger display of the count down.

Done (I hope). I've enlarged the countdown display and given it a slightly different font, so it's much more visible. As for the time selection field, what I've done with my latest version (not yet uploaded, see below) is to have the cursor automatically jump to the end of the minutes section of the time field when you start the app. Like this: 25|00
This should be more convenient than starting at the very front or end of the field (like |2500 which it currently does, or 2500| which is the next best option). I've decided to stay with my original idea of not using separate fields for hours/minutes/seconds, for the reasons I've already explained.

Quote:

Also, ability to set alerts before the timer expires.. like if it is a 15min count down, I would like to set multiple alerts at 10, 5, 1 minutes, etc. This would be helpful for chairing time-limited talks, etc.
P

I've done a version of this as well, but before I upload it I wanted to get a general opinion on what would be more useful: a) repeating sub-alerts, e.g. every 5 minutes or 2 minutes or whatever until the total countdown is done and the final alert sounds; or b) a non-repeating x-minute warning, e.g. a single 5-minute or 2-minute warning before the countdown is done.

Actually, I could probably do this as a user-selectable option, now that I think about it. So you could chose either a non-repeating x-minute warning or a repeating x-minute alert until the final alert sounds, or none.

Let me know what you guys think. I may just go with this last idea, since it will be fairly easy to extend what I've already started.

I'll wait a day or so for some more input before uploading the new version, but if no one responds I'll go with my last idea.

Thanks for the input so far!

Inphektion · **OS:** 5.0.0.351

I think you should have two optional sections for user to configure alerts before timer hits 0.

So they set their time, lets say 2500
then there is an Optional alert section with two areas that can be configured

Sound alert at __x1__ time and then repeat every _x2__ time(s).
Sound alert at __y1__ time and then repeat every _y2__ time(s).

so for an example they could sound alert at 1500 and repeat 0 times
then sound alert at 500 and repeat every minute.

This gives the user the ability to set a "marker" so to speak but then a separate repeating interval.

With your way I could only have one non repeating alert or a repeating one.
So the user couldn't alert when 10 minutes are left and then every minute for the last 3. With the options above they could.
and a user could enter a value for x1 or nothing else or x1, x2. or x1 y1. or x1, y1 y2.

obijohn · 09-22-2006, 04:38 PM

Hmmm, this sort of sounds like a cascading alert. I realize it's not what you meant exactly, but it is another nice idea (I think). For example, a cascading alert would sound whenever the remaining time is 50% of the elapsed time since the previous alert. So if you set the timer for 20 minutes, it would go off with 10 minutes remaining, then 5 more remaining, then 2.5 minutes remaining... etc. Of course there would have to be a cutoff at, for example, the 30 second mark.

Anyway, that's not exactly what you mean, but I like the idea so I may incorporate it as well.

obijohn · 09-24-2006, 08:33 AM

I've incorporated some of the suggested changes. See the first post in this thread for the updated readme.txt file which explains all the changes.

Enjoy!

patrickh · 09-24-2006, 11:27 AM

You need a reset timer menu item / button..

I also suggest a quick double-ESC to minimize (move to background)..

obijohn · 09-24-2006, 12:50 PM

Quote:

Originally Posted by patrickh

You need a reset timer menu item / button..

Will do. Can't believe I didn't catch that one myself!

Quote:

I also suggest a quick double-ESC to minimize (move to background)..

Good idea. With the shortcut minimize keys and double-ESC, I can probably remove the Minimize button altogether. Should I leave it, or no?

obijohn · 09-24-2006, 05:36 PM

Ok, suggestions again incorporated into new version. See first post in thread.

cooperpwc · 09-24-2006, 08:53 PM

Quote:

Originally Posted by obijohn

Unfortunately, RIM has not exposed an API that allows apps to play the tones and alerts already stored on the phone; the app has to create it's own, and the options are limited.

The interesting thing is that the folks at RexWireless have found a way to tap into the Blackberry tunes and alerts system. ToDoMatrix adds itself as setting that can be fully adjusted in each profile. I'm not suggesting that you would want to go that far for your Timer app (which I'm about to test) but I thought that it would interest you to know.

cooperpwc · 09-24-2006, 09:09 PM

Perfect simple app. Thanks! It's a keeper.

PaCharger · 09-24-2006, 09:30 PM

pretty cool utility. I never carry a watch, or a stopwatch...now this will come in handy for a ton of stuff.

Added this and the NFL tracker, both pretty awesome tools.

Thanks!

JSanders · 09-24-2006, 10:54 PM

Great App, I've used it as timekeeper for my child's soccer games.

obijohn · 09-25-2006, 06:00 AM

Quote:

Originally Posted by cooperpwc

The interesting thing is that the folks at RexWireless have found a way to tap into the Blackberry tunes and alerts system. ToDoMatrix adds itself as setting that can be fully adjusted in each profile. I'm not suggesting that you would want to go that far for your Timer app (which I'm about to test) but I thought that it would interest you to know.

There are a couple of problems with this.
1) Implementing the feature you describe requires code signing keys issued by RIM (and paid for by the developer). Since I'm releasing this free, I can't afford to pay for the keys. I guess if I was going to charge $59 for an app like ToDoMatrix, then maybe I would consider it as an option.
2) Even if I paid for the keys, this type of alert can only be set by the user outside the app by editing the device profiles. There is no way to select and play a device ringtone/tune directly within an app.

Basically, the app itself cannot access the tunes on the device at all. For some reason, RIM just doesn't allow this. The way the above method works is the app issues a "play notification alert" command and whatever alert tune has been assigned in the user profile will play. And to do this requires the developer paying for code signing keys to get access to the necessary commands to create and access settings in the profiles.

To me, this whole thing is idiotic. Let's say I wrote a countdown timer for Windows. Can you imagine having to open the Windows Control Panel and edit the system Sound Properties to assign a particular tune for the timer to play, instead of simply being able to assign it in the application itself? And on top of this, Microsoft charging the developer a fee for the privilege of using such a wonderful setup? That's just crazy!

Inphektion · **OS:** 5.0.0.351

The alerts don't make any noise for me, vibrate or tone.
I'm on the 8100.
Also how hard to add stopwatch functionality? Even just a basic one without split time works for me.

cooperpwc · 09-25-2006, 10:40 AM

Quote:

Originally Posted by obijohn

There are a couple of problems with this.
1) Implementing the feature you describe requires code signing keys issued by RIM (and paid for by the developer). Since I'm releasing this free, I can't afford to pay for the keys. I guess if I was going to charge $59 for an app like ToDoMatrix, then maybe I would consider it as an option.
2) Even if I paid for the keys, this type of alert can only be set by the user outside the app by editing the device profiles. There is no way to select and play a device ringtone/tune directly within an app.

Basically, the app itself cannot access the tunes on the device at all. For some reason, RIM just doesn't allow this. The way the above method works is the app issues a "play notification alert" command and whatever alert tune has been assigned in the user profile will play. And to do this requires the developer paying for code signing keys to get access to the necessary commands to create and access settings in the profiles.

To me, this whole thing is idiotic. Let's say I wrote a countdown timer for Windows. Can you imagine having to open the Windows Control Panel and edit the system Sound Properties to assign a particular tune for the timer to play, instead of simply being able to assign it in the application itself? And on top of this, Microsoft charging the developer a fee for the privilege of using such a wonderful setup? That's just crazy!

I quite agree. And thanks for the explanation. Is it possible to have a choice of a shriller alert (since there is appparently a volume limitation.) For example, you can download an excellent alert at Blackberry Extras called Notifier_EarlierRiserF. It actually sounds pretty nice but at normal volume you cannot miss it. Also having the option of the alert repeating a few times when time has run out would be great.
Just suggestions. The app is already excellent.

obijohn · 09-25-2006, 12:28 PM

Quote:

Originally Posted by Inphektion

The alerts don't make any noise for me, vibrate or tone.
I'm on the 8100.

Hmm, that's very odd. I'm pretty sure the 8100 uses OS version 4.2, could you check your version for me? The tone and vibrate functions should work on all OS versions 4.0 and up, at least according to the API docs. I don't know what the problem could be. Please double-check your OS version for me and I'll start digging around the API documentation for 4.2 and see if I can figure out what the problem might be.

Quote:

Also how hard to add stopwatch functionality? Even just a basic one without split time works for me.

Well, this is a count down timer, after all. ;) One possibility, though, would be to allow the "T-Minus" display to reverse and count up from 0, in which case the text would need to change to "T-Plus" (or something) while in this mode. Tell you what, if one other person besides you posts a response here that they also would like this option, I'll add it. Deal?

obijohn · 09-25-2006, 12:49 PM

Quote:

Originally Posted by cooperpwc

Is it possible to have a choice of a shriller alert (since there is appparently a volume limitation.)

One possibility I've played around with is having a high-pitched chromatic scale ascending very rapidly. This is not really louder but it is more noticeable (the alert is already at 100% volume, some more RIM brain damage in not allowing developers to do what they want). I may add this as an option in a later update.

Quote:

Also having the option of the alert repeating a few times when time has run out would be great.

What I've thought about in this regard is an "annoy me" option, which will cause the alert tone to repeat continuously until manually stopped, similar to an alarm clock which has to be turned off once the alarm sounds. It could also go into a kind of "haywire" mode after a certain period of time, playing random notes all over the place instead of just repeating the same tune over and over. Anyway, this kind of thing is definitely doable in the next update.

Quote:

Just suggestions. The app is already excellent.

Thanks, glad you like it! And keep the suggestions coming (within reason, of course; I don't want to overload the thing with features to the point where it's no longer simple and easy to use).

obijohn · 09-25-2006, 01:05 PM

Quote:

Originally Posted by obijohn

Quote:

The alerts don't make any noise for me, vibrate or tone.
I'm on the 8100.

Hmm, that's very odd. I'm pretty sure the 8100 uses OS version 4.2, could you check your version for me? The tone and vibrate functions should work on all OS versions 4.0 and up, at least according to the API docs. I don't know what the problem could be. Please double-check your OS version for me and I'll start digging around the API documentation for 4.2 and see if I can figure out what the problem might be.

I just pulled up the 4.2 API docs, and the routines I use to play the tone and vibrate have definitely not changed, and in fact the 4.2 API says they are the same as 4.0. I can see no reason why it shouldn't be working. If someone else who has the new 8100 could try it out for me and verify there is a problem, I'd appreciate it!

obijohn · 09-25-2006, 01:23 PM

Quote:

Originally Posted by obijohn

I just pulled up the 4.2 API docs, and the routines I use to play the tone and vibrate have definitely not changed, and in fact the 4.2 API says they are the same as 4.0. I can see no reason why it shouldn't be working. If someone else who has the new 8100 could try it out for me and verify there is a problem, I'd appreciate it!

Okay, I downloaded the 8100 Simulator (for some reason it wasn't included in the Simulator Pack for the JDE), and the alerts, both tone and vibrate, all work fine. Are you sure you didn't have your phone on silent mode?

Inphektion · **OS:** 5.0.0.351

Well i had on quiet profile but just changed to normal and didn't hear anything.
version is 4.2.0.42

I have a stopwatch program that I load via alx and it works but it would be nice IMO to just have one program be able to count up or down for me.
You could just have a radio button that has Timer Mode and one that says Stopwatch mode. When it stopwatch mode T-Minus could say t-plus or time and Start timer button could just say start no matter what mode you are in.

ANYONE ELSE WANT THIS FUNCTIONALITY?

obijohn · 09-25-2006, 05:10 PM

Quote:

Originally Posted by Inphektion

Well i had on quiet profile but just changed to normal and didn't hear anything.
version is 4.2.0.42

It works perfectly in the 8100 Simulator (the Simulator even "shakes" when it vibrates). In the simulator, on the device itself, I went to Options->About and it says "v4.2.0.42 (Platform)" so I don't know what to tell you about why yours isn't working.

If someone else who has an 8100 could confirm that the tone and vibrate either work or don't work, I really would appreciate it. This is bugging the heck out of me right now, because everything on my end says it should work on the 8100.

Quote:

I have a stopwatch program that I load via alx and it works but it would be nice IMO to just have one program be able to count up or down for me.
You could just have a radio button that has Timer Mode and one that says Stopwatch mode. When it stopwatch mode T-Minus could say t-plus or time and Start timer button could just say start no matter what mode you are in.

ANYONE ELSE WANT THIS FUNCTIONALITY?

If I implement a "count up" option, it would either: A) stop when it reaches the time entered in the time entry field, in which case alerts would still work; or B) only stop when you click the Pause/Stop button, as a regular stopwatch does, in which case it could continue indefinitely and alerts would make no sense in that context, and neither would the main time entry field.

Option A is certainly doable, but not very useful for a general-purpose stopwatch. Still, if all you want to do is time something, and you know in advance that it's not going to take longer than X amount of time, you could enter that maximum value of X in the time entry field and then the "count up" option would function as a simple elapsed-time indicator. However, the timer would still stop on its own when it reaches that maximum value of X in the time entry field (and play alerts if they were enabled). This option is fairly easy to implement.

On the other hand, option B begins to add a level of complexity to the app that I was trying to avoid, even though it may not appear that much different on the surface than option A.

Inphektion · **OS:** 5.0.0.351

Yea i'm not running races. Most things I need a stopwatch for are under 5 minutes. I could always use the countdown timer entering like 6000 and go from there but just though it would be nice to add stopwatch functionality. Not a big deal though if it is a hassle in any way. I'll keep messing with the alerts and profiles see if i can get it to work.

anesone · 09-26-2006, 09:30 PM

I tried out the countdown timer and had a problem.
The final countdown doesn't go off for me. I have my profile set to Normal.
I have the timer set to 500, Alert 1 set to 400, alert 2 set for 100, and Vibrate and Restore are checked. Alerts 1 and 2 work fine (short vibration), but the final alert does not do anything. It does restore, but no vibration. When I check the Tone option, Alerts 1 and 2 only trigger a tone (no vibrate), but the final alert does sound a tone and vibrates.

I have an 8700g, OS4.1.0.284.

Any thoughts as to why vibrate only doesn't work?

obijohn · 09-27-2006, 05:01 AM

Quote:

Originally Posted by anesone

I tried out the countdown timer and had a problem.
The final countdown doesn't go off for me. I have my profile set to Normal.
I have the timer set to 500, Alert 1 set to 400, alert 2 set for 100, and Vibrate and Restore are checked. Alerts 1 and 2 work fine (short vibration), but the final alert does not do anything. It does restore, but no vibration. When I check the Tone option, Alerts 1 and 2 only trigger a tone (no vibrate), but the final alert does sound a tone and vibrates.

I have an 8700g, OS4.1.0.284.

Any thoughts as to why vibrate only doesn't work?

First, there is a stupid bug with the "vibrate only" setting. This is probably what you're describing. It is fixed in the latest update (version 0.5) which I should be uploading some time this morning.

Second, setting Alert 1 to 400 and Alert 2 to 100 wouldn't work with the timer set at 500. The alerts don't have a "seconds" part, so your setting would have Alert 1 sounding at the 4-hour mark, and since the main timer starts at 5 minutes it would never sound. But since you got the short vibration that they make in a "vibrate only" mode, I assume you have them set to 4 and 1, right? Or maybe you had Repeat Every set to 1?

Also, the secondary alerts do not vibrate unless the main alert is "vibrate only". This is a feature, not a bug.

The reasoning behind having them "tone only" unless the main alert is "vibrate only", is that you could have the main timer set at (for example) 2 hours, with the repeating alert set to go off every minute, and it would probably not be very good for your device to have it vibrate 120 times in the span of 2 hours. I supposed I could have tone and vibrate settings for each secondary alert, but I didn't want to clutter things up with that many options.

Anyway, the first vibrate problem you described has been fixed in version 0.5. There are a couple of new features as well, so you might want to upgrade when I post it.

Inphektion · **OS:** 5.0.0.351

I got an "uncaught exception" today.
Looking at the log on the pearl it had this:

Code:

Name: NumberFormatException
GUID: 9c3cd62e3320b498
Time: Sep 27, 2006 07:28:42
No detail message
net_rim_cldc-9
 NumberUtilities
 parseInt
 0x6C5B
net_rim_cldc
 Integer
 parseInt
 0x7365
net_rim_cldc
 Integer
 valueOf
 0x73AE
CountDown
 CountDown
 fieldChanged
 0xED
net_rim_cldc-5
 Field
 fieldChangeNotify
 0x1BE6
net_rim_cldc-7
 ButtonField
 trackwheelClick
 0x5816
net_rim_cldc-6
 Manager
 trackwheelClick
 0x54BF
net_rim_cldc-6
 Manager
 trackwheelClick
 0x54BF
net_rim_cldc-6
 Manager
 trackwheelClick
 0x54BF
net_rim_cldc-6
 Screen
 trackwheelClick
 0x815A
net_rim_cldc-6
 Screen
 dispatchNavigationEvent
 0x6A58
net_rim_cldc-6
 UiEngineImpl
 processMessage
 0xA99D
net_rim_cldc-4
 Application
 processNextMessage
 0xEE3
net_rim_cldc-4
 Application
 enterEventDispatcher
 0x6A0
CountDown
 CountDown
 main
 0x567

Inphektion · **OS:** 5.0.0.351

Also the main alert works I just can't get the intermediate ones to do anything.

obijohn · 09-27-2006, 12:30 PM

Inphektion, the exception you saw was probably caused by pressing the Start button with a blank timer or alert field. This bug has been fixed in version 0.5 (just uploaded). Also, make sure your secondary alert times don't contain seconds (i.e., an alert time of 400 would be 4 hours, not 4 minutes). Anyway, install the new version and let me know if you still have any problems.

Version 0.5 also fixes a couple of other bugs (two little ones, and the "vibrate only" bug mention in a previous post). It also adds a couple of features, including an "elapsed time" mode, and an optional fast-and-high-pitched alert tune.

obijohn · 09-27-2006, 02:26 PM

Inphektion, I notice you mentioned you ran it on a Pearl, so I switched back over to the 8100 simulator. Everything seems to work fine, the secondary alerts sound when they are supposed to, no random crashes, etc. But danged if the display doesn't wrap part of the "Elapsed" checkbox. *Pfft*. I'm uploading a quick update which takes the narrower display into account. I thought the display was the same size on the 8100 as the 7100. Oh well.

I've posted an update (0.5.1) to fix this display issue on the Pearl.

obijohn · 09-27-2006, 02:37 PM

With the latest release (0.5.1) all the features which have been suggested that I think should be included are there, and most of the major bugs have been ironed out (I think, I hope). I don't plan on adding any new features, unless someone suggests something that is glaringly absent or obvious, and instead I will concentrate on fixing any bugs or issues that pop up on the various models and OS versions which are floating around.

Anyone who has mentioned or noticed a problem/bug in the past, please update to 0.5.1 and let me know if the problem is resolved in this release.

Thanks everyone!

Inphektion · **OS:** 5.0.0.351

ahh. I finally get it.
I had startT at 200 and then alert at 100 or 30.
with startT at 230 and then alert at 2 and second alert at 1 it works. There is no description in the fields that format for time changes between start T and the alerts. Can you make alerts same format as startT so I can have an alert at 30 seconds? Or if you don't want to make any major changes can you label that the alert needs to be in minutes not seconds like startT?

If i put in 6000 to get one hour, hit pause, reset and start the startT time changes to 10000 and then counts down correctly starting with 5959. Weird. What is the max time supported? is 5959 the max?
If I put in 9000 to do an hour and a half it starts counting down from 13000...

clearly i'm all confused with the time entry here but I think others would be too then.

Inphektion · **OS:** 5.0.0.351

ok i see. 13000 is really 1:30:00 in HH MM ss.
and the alert field is HH MM no seconds, correct?
so in alert field if i entered 129 it would alert after 1 minute with the above start time?

I get it now and its completely useable but there has to be a way to make this easier for someone who just installs it and wants to use it.

obijohn · 09-27-2006, 04:28 PM

Quote:

Originally Posted by Inphektion

ahh. I finally get it.
I had startT at 200 and then alert at 100 or 30.
with startT at 230 and then alert at 2 and second alert at 1 it works. There is no description in the fields that format for time changes between start T and the alerts. Can you make alerts same format as startT so I can have an alert at 30 seconds? Or if you don't want to make any major changes can you label that the alert needs to be in minutes not seconds like startT?

If i put in 6000 to get one hour, hit pause, reset and start the startT time changes to 10000 and then counts down correctly starting with 5959. Weird. What is the max time supported? is 5959 the max?
If I put in 9000 to do an hour and a half it starts counting down from 13000...

clearly i'm all confused with the time entry here but I think others would be too then.

Okay, maybe I should explain it better in the docs. Basically, the time value you input into the main time entry field ("Start T") is corrected for you if it doesn't match the format a clock would use (HHMMSS). That's why when you input 6000 for 1 hour, it converts it to 10000 at the start of the count down. A clock would never display 1 hour as 60 minutes, it would display it as 1:00:00. After 1 second has elapsed, the current time would be 59 minutes 59 seconds remaining, which is what you saw happen. I guess I thought this would be fairly intuitive, maybe I was wrong.

And yes, if you input 9000 it would be converted to 1 hour 30 minutes, because a clock wouldn't display 1 hour 30 minutes as 90. My microwave does this too when I enter 90 seconds (converts the display to 1 minute 30 seconds) so I didn't think it would be that confusing.

I guess adding to the confusion is the fact that the secondary alerts don't use seconds (entering 10 here is read as 10 minutes, not 10 seconds). Both of these decisions were made with the idea of entering values quickly. I figured that no one would want an alert to repeat every 2 seconds.

FAIR WARNING! If this continues to be a problem for people, I will change the secondary alert format to include seconds, although this may cause problems for people who are used to the current format.

The maximum time is 9999 hours 59 minutes 59 seconds (1 second shy of 10,000 hours; well over 1 year). Now that you mention it, I don't really check against this maximum value since I figured no one would actually try to input a time that large, but I probably should. If you tried to input 9999 hours, 99 minutes, 99 seconds, it would cause an overflow since it's more than 10,000 hours. I see a version 0.5.2 around the corner to catch this...

anesone · 09-27-2006, 05:10 PM

Quote:

Originally Posted by obijohn

First, there is a stupid bug with the "vibrate only" setting. This is probably what you're describing. It is fixed in the latest update (version 0.5) which I should be uploading some time this morning.

Second, setting Alert 1 to 400 and Alert 2 to 100 wouldn't work with the timer set at 500. The alerts don't have a "seconds" part, so your setting would have Alert 1 sounding at the 4-hour mark, and since the main timer starts at 5 minutes it would never sound. But since you got the short vibration that they make in a "vibrate only" mode, I assume you have them set to 4 and 1, right? Or maybe you had Repeat Every set to 1?

Also, the secondary alerts do not vibrate unless the main alert is "vibrate only". This is a feature, not a bug.

The reasoning behind having them "tone only" unless the main alert is "vibrate only", is that you could have the main timer set at (for example) 2 hours, with the repeating alert set to go off every minute, and it would probably not be very good for your device to have it vibrate 120 times in the span of 2 hours. I supposed I could have tone and vibrate settings for each secondary alert, but I didn't want to clutter things up with that many options.

Anyway, the first vibrate problem you described has been fixed in version 0.5. There are a couple of new features as well, so you might want to upgrade when I post it.

You are correct...I did have Alert 1 set to 4 and Alert 2 to 1. I look forward to testing out the new version. Great app btw.