HI Stevie Mac,
Thanks for a great program!
1. I found one bug:
Editing alert File only (without changing alert enable or other options) fails (setting is forgotten). There is no "apply" button and rather an "open" button when editing alerts. The workaround is to twiddle some other setting and hit "apply".
I noticed this on a previous release - I thought I'd solved it! no matter, I've actually noticed the Backlight and stay on top settings are also forgotten! I'll sort these small issues for the next release.
Suggestions
2. What does Backlight "full, half, default" mean - it doesn't seem to do anything on my Orange C600 WM5 phone. Also, what would 'default' correspond to?
I have found this to be an issue on the SP5 also (smartphone like C600 but with WiFi) . The Full refers to keeping the backlight on fully. The half refers to the level your backlight dims to prior to going off completely, default is as it is set in power management (i.e. off after xx seconds). It seems this doesn't work as expected on WM2005 devices & I will have to do some digging.
3. Allow Timer sets to be given names, included when building the report.
I had thought about this but was unsure if it was worth the effort.
4. Text entry method defaults to T9 even though I reset to 'abc' every time. Other apps seem to know I want 'abc' (I use different languages without T9).
Yeah, my bad (or rather my good!) I set this as it its what 'I' wanted, I'll disable the 'force to T9' on the text boxes!
5a. Another journal mode that keeps history: report would include multiple times the journal watch was pressed, not just the most recent one as now. Useful to keep track of multiple time points, without having to create a journal for each.
I like your idea, I'll consider it!
'Multi-Journal'. Hmmm, I'll give it some thought.
5b. Somebody earlier suggested adding specialized modes e.g. 'count down, beep, start counting up'.
However, this would clutter the app.
If at all needed, a cleaner alternative would be to allow custom compositions as a sequence of actions.
Not quite sure what you are saying exactly!. I did not disregard the comments other made, I simply haven't had time to explore their requests so have came to no decisions yet but I do remember thinking it would clutter the app. Be more explicit if you think you have a good idea on this matter.
6. Allow customizable time increment display. E.g. 1/100 sec, 1/10 sec, sec, min. I don't think 1/100 is a good default as it probably isn't accurate. E.g. when the timer stops it displays 0.06. Perhaps 1/10 would be better.
I tried to have the timers as accurate as possible, but alas, it is operated by a human who can add around 0.2 sec (I recently read: For most people, the time from eye to reaction is around 0.3 sec, random error or uncertainty: ± 0.2 sec). So I guess I was a little over zealous when I developed this! As for general accuracy, the timings are as accurate as the clock on your phone!
7. Does running the timer increase power consumption?
Can it be reduced by checking timer interrupts less often? E.g. 1/min.
Yes, I believe it does increase power usage. I do actually minimise redrawing to the invalid part of the screen to reduce the drain. Additionally, when the program is in the background, updates are reduced & timings are recalculated when the app is brought to the fore. More: If i did reduce the timing to 1/10 sec, then less update logic would be executed, further reducing consumption! Lastly, using the backlight obviously reduces battery life & as you have already noticed, this can be set to 'default'.
8. A key lock mode: i am afraid of starting/stopping a timer by accident while wanting to see the app on top; how about a special key lock mode that requires pressing a special combination to unlock. The phone has key lock but then stopwatch goes to the background and doesn't display.
Pressing 'Home' or 'Back' has no effect on this application. Use these keys to navigate other apps. Though I do take your point. I suppose an app lock of sorts is not an unreasonable request.
9. Comment on file format of Timer sets so they can be edited on a computer and copied.
These are very simple 'ini' style files I'm sure you can work them out.
Here is 2 examples...
timer1.lastvalue=0
timer1.setvalue=300000
timer1.caption=5 Min Reminder
timer1.mode=countsup
timer1.soundenabled=WAV
timer1.soundfile=\Windows\Dogbark.wav
timer2.lastvalue=180000
timer2.setvalue=180000
timer2.caption=Small Egg
timer2.mode=countsdown
timer2.soundenabled=Vibrate
timer2.soundfile=\Windows\Default.wav
and yes, documentation would be nice, so would an assistant
These ini files are saved in the same directory as the application as Set1.ini, Set2.ini ...
10. Allow alerts to repeat 1,2,3 .. times or until dismissed. (this can be covedrd by 5) though.
Effort vs benefit! I will consider it.
11. (minor) The light background with bitmaps make it a bit hard to read the text. i assume one can customize by replacing the bitmap file; perhaps worthe commenting on.
Yes, you are correct. The file 'config.ini' can be edited / or you can replace the bitmaps.
The config file and bitmaps are saved in the same directory as the application.
12. (minor) Build report is somewhat sluggish. Perhaps a text only mode would be faster.
If I get around to it, I'll look into why this is sluggish.
I hope I haven't made too many requests at once... Just ideas - it's a great app already.
Thanks again for great work.
--- clearstar
Your welcome.
I can't promise anything at the moment, I struggle for time these days!
Steve.
5
MisterOrange, on Jul 13 2006, 00:06, said:
News + Articles
Sign In
Create Account
Back to top