Req: tiny systray alarm/timer

  • Thread starter Thread starter Canetoad
  • Start date Start date
C

Canetoad

Nothing fancy. Only requirement is it sits in the systray, counts down
hours/minutes, then sounds an alert when time is up.
Thank you
 
Canetoad said:
Nothing fancy. Only requirement is it sits in the systray, counts down
hours/minutes, then sounds an alert when time is up.

You can use a utility like RBTray to minimize most any (99%) windows
to tray. However, if you want the remaining time remaining to show up
as status in the minimized tray icon, then you would need a timer with
its own min-to-tray function built-in. Is this second part a req?

My favorite countdown timer is 1Time. Yet don't know if I can recommend
it to you, because of the factor of its time-remaining only showing
accurately on the task bar -- and not when RBTray minimizes it off the
taskbar and into the tray.

I've collected a large number of countdown timers. If indeed you wanted
specifically one with its own minimize-to-tray function, I could assess
for candidates...
 
You can use a utility like RBTray to minimize most any (99%) windows
to tray. However, if you want the remaining time remaining to show up
as status in the minimized tray icon, then you would need a timer with
its own min-to-tray function built-in. Is this second part a req?

My favorite countdown timer is 1Time. Yet don't know if I can recommend
it to you, because of the factor of its time-remaining only showing
accurately on the task bar -- and not when RBTray minimizes it off the
taskbar and into the tray.

I've collected a large number of countdown timers. If indeed you wanted
specifically one with its own minimize-to-tray function, I could assess
for candidates...

No, don't need to see time remaining. Just hear the alarm when time is
up. (Situation:office computer, crowded taskbar, parking meter....)Any
suggestions would be appreciated.
Thanks
 
--Snip--
No, don't need to see time remaining. Just hear the alarm when time is
up. (Situation:office computer, crowded taskbar, parking meter....)Any
suggestions would be appreciated.
Thanks

=== I have tried a few , but the one I use is " MultiTimer " from ...
http://www.programming.de/ ........

-from the site--
Multi Timer (Freeware)
Ten independent Timers in one program, to count down to zero or up to
max. 100 hours, with 1 second accuracy. Timers can be viewed one by
one or all at once and can resume on a later computer session, all
settings are remembered from the previous time ran. Sound signal
(optional) and blinking message window (cannot be hidden with other
windows) with user-defined message on alarm. Each timer can be
assigned an individual identifier string. Always on top mode and hide
in System Tray mode. =========
 
=== I have tried a few , but the one I use is " MultiTimer " from ...
http://www.programming.de/ ........

Thanks, I'll give it a try. btw, many good looking programs on this site
but I was especially impressed by their mission statement, so here it is
for others to read:

Mission Statement
If you love it, you can learn it. If you've learned it you can get
experience in it. Age doesn't matter. Strive for wisdom and personal
understanding. Know that your way might not be the best, and also that
other's views may not apply to you. Live at peace with each other. Help
those who are truly seeking and need only the tools to begin their
journey. Be patient in teaching, and respect the fact that another may
be weak in the area that you're strong in, and that they may have a
strength that you don't know how to develop. Correct each other in truth
and logic. Code for others as you would have them code for you. Live
long and program.
(White Flame)
 
Canetoad said:
No, don't need to see time remaining. Just hear the alarm when time is
up. (Situation:office computer, crowded taskbar, parking meter....)Any
suggestions would be appreciated.

I put together a list of five candidates. Of all of them, I came to
conclude that TClock Light is the most attractive option. I know your
subject says "tiny alarm/timer," and that's not how we think of TClock.
Yet its other functions can be ignored. It is light and unobtrusive,
and its countdown (and alarm) features are very smooth.

I see in this thread that Multi Timer already got recommended. That's
definitely a good option. And it does already have the tray mode built
in (unlike several others I assessed).

http://www.redshift.com/~omega/clips/alarms/ttimers.htm

As to my previous mention of 1Time. I have to conclude that I won't
be able to promote 1Time for your usage. It is tricky to tray it, even
with RBTray. (I manage to do it on my system only because it loads earlier
in my startup than does RBTRay -- that which would not be a natural
order those who do not make 1Time quite such a major inhabitant in their
environment.)
 
omega said:
As to my previous mention of 1Time. I have to conclude that I won't
be able to promote 1Time for your usage. It is tricky to tray it, even
with RBTray. (I manage to do it on my system only because it loads earlier
in my startup than does RBTRay -- that which would not be a natural
order those who do not make 1Time quite such a major inhabitant in their
environment.)

It trays easy using The Wonderful Icon :-)
 
Canetoad said:
I have tried a few , but the one I use is " MultiTimer " from ...
http://www.programming.de/ ........

Thanks, I'll give it a try. btw, many good looking programs on this site
but I was especially impressed by their mission statement, so here it is
for others to read:

Mission Statement
If you love it, you can learn it. [...]

Each of the last two last lines would be great for putting on coffee mugs
(or bumper stickers, t-shirts, etc).
 
jo said:
Oh. Pooh. No it doesn't. It leaves a useless icon on the taskbar also...

I'm pretty convinced no trayer can solve the 1Time situation.

Another I've tried for this is TrayIt, which is a pretty adept utility
<http://www.teamcti.com/trayit/trayit.htm>, but it too fails.

The closest solution, RBTray, it makes for a tricky set of rules. First
that 1Time has to be the first launched of the two, and stay loaded for
subsequent success. Then there is the further matter that successfully
traying can be had strictly via the menu click on the icon in the taskbar.

I once sent a mail to the author of 1Time, to thank him for the program.
At the time, he said that I'd inspired him enough that he was thinking
of refining 1Time a bit more. Unfortunately, since I only do email about
three times a year, and did not even see his message for a while, then
badly flaked about ever replying...that correspondence dropped as fast
as it had begun. I figure I've sort of forfeited my chance of requesting
he recode anything. (Unless I start anew with a bribe or something.)
 
jo said:
MinMaxExtender trays it flawlessly, no matter what.
http://www.monctoncomputerservice.com/revenger_inc/mmext.html

Hey, yep, checking it out, and see you're right.

One project I'd done this year, it was to analyze more than a dozen
minimizers. One of the main items I'd assessed on them was their
handling for various problem windows. Such as those of 16-bit programs.
And for various difficult cases, examples 1Time and Notebark, where they
all failed.

I did have MinMaxExtender, but it wasn't part of that analysis. I'd
ended by cataloging it instead into in my directory for winsizers (for
its other functions, including the rollup to titlebar size). At the time
I'd looked at it, its min-to-tray function had not looked very good, for
a couple of reasons.

One reason was that it did a take-over/overwrite on the titlebar of my
explorer windows, taking away my access to the icons from my add-in prog
which gives me an MRU for recent folders. After your post, though, I took
a closer look. Found that it allows me to configure program or windows
into its exclusion list. So by excluding it there, I was able to instead
keep my needed icons in the explorer window titlebars.

The remaining MinMaxExtender drawback that I'd noted - the first one now
scratched off list - it's that the little grey buttons stand out in an
ugly way. It would be better if it could adapt itself to the windows color
scheme in use on the system.

The one remaining matter, which I've not checked, it's whether there is
any notable impact on system performance. First, compatibility, with its
hooking. (A few of the trayers can misbehave a bit.) This can take time
to experiment with, requires running the program all the time for a while.
Then the second item: memory and resource use. That's complicated there,
too. The only physical fact I've got is that the size of exe + dll = 500k.
Although of course that doesn't answer the question of mem & resources
usage...

But anyway, to the point of the topic. I now wish to retract the statement
I'd made earlier in this thread: "I'm pretty convinced no trayer can solve
the 1Time situation."

For problem windows, MinMaxExtender succeeds where a dozen other trayers
fail.

But, Jo, one thing. You do realize the /consequence/ of your info, in the
war of the trayers?

MinMaxExtender RULEZ !
TheWonderfulIcon SUX !
 
omega said:
Hey, yep, checking it out, and see you're right.

One project I'd done this year, it was to analyze more than a dozen
minimizers. One of the main items I'd assessed on them was their
handling for various problem windows. Such as those of 16-bit programs.
And for various difficult cases, examples 1Time and Notebark, where they
all failed.

The purist in me also wants to see intelliigent handling of those apps
which are designed to minimise to the tray anyway. Power-Grab, for
example. Minimising it to tray with TWI or MME gives two tray icons. Ok,
one should minimise it conventionally, but....
I did have MinMaxExtender, but it wasn't part of that analysis. I'd
ended by cataloging it instead into in my directory for winsizers (for
its other functions, including the rollup to titlebar size). At the time
I'd looked at it, its min-to-tray function had not looked very good, for
a couple of reasons.
The remaining MinMaxExtender drawback that I'd noted - the first one now
scratched off list - it's that the little grey buttons stand out in an
ugly way. It would be better if it could adapt itself to the windows color
scheme in use on the system.

Are you adapting? Or going in with a resource hacker?

The drawback for me is the fact that it doesn't work properly on a
maximised window. Since I'm having a closer look at it atm, I'm going
with the workround of stretching the window sideways and then upwards
but I'd much rather not have to.
The one remaining matter, which I've not checked, it's whether there is
any notable impact on system performance. First, compatibility, with its
hooking. (A few of the trayers can misbehave a bit.) This can take time
to experiment with, requires running the program all the time for a while.
Then the second item: memory and resource use. That's complicated there,
too. The only physical fact I've got is that the size of exe + dll = 500k.
Although of course that doesn't answer the question of mem & resources
usage...

It doesn't feel like it uses much at all. I'm going to keep running it
for a while and see how it shapes up.
IIRC Actual Title Buttons has recently gone freeware, and is a joke
compared to MME
But anyway, to the point of the topic. I now wish to retract the statement
I'd made earlier in this thread: "I'm pretty convinced no trayer can solve
the 1Time situation."

Yay. Gotcha. :-)
For problem windows, MinMaxExtender succeeds where a dozen other trayers
fail.

But, Jo, one thing. You do realize the /consequence/ of your info, in the
war of the trayers?

MinMaxExtender RULEZ !
TheWonderfulIcon SUX !

TWI doesn't miss very often. And of course, it can tray by hot key which
is nice. And it does millions of other stuff. But I am slowly moving
away from it *sob* since switching to RunFast as an app launcher. The
main problem with TWI is that it overwrites app specific hot keys. This
can be a real nuisance at times. It is odd how many hot keys you can
keep in your mind and know nothing about until in the relevant app
window... when you find you've assigned the combination to some obscure
task in TWI :-(
But it's still a superb app - I doubt it will ever be out of my sys
tray. AFAIK, all it does is load a reg file on launch - I doubt it uses
any resources just sitting in the tray.
 
jo said:
The purist in me also wants to see intelliigent handling of those apps
which are designed to minimise to the tray anyway. Power-Grab, for
example. Minimising it to tray with TWI or MME gives two tray icons.

Yes, that's a major problem area: the group of program having their own
min-to-tray function. To me, it's a big pain when programs have this.
The ideal design would be that things were taken of at the OS level.

Such that a direct click on the minimize button of a window always meant
"minimize to taskbar" and the "right click on the minimize button always
meant "minimize to tray."

(I mean at least for standard programs. Those whose character is to be
tray apps anyway, where most of their commands are performed from their
tray icon menu, that's a separate situation.)
Ok, one should minimise it conventionally, but....

Yes, but it is tricky to try to keep one's reflexes tracking which click
is the applicable one for which kind of minimize for which app.

You know, the group of programs having their own min-to-tray function,
I've noticed some of them generate -- all on their own -- problems of
the double icons. Two examples: Treepad, and FreshDownload. On both
of these, I have their minimize to tray option turned off. Yet they are
constantly shoving their icon into my system tray. Together with another
icon in my taskbar. All for just one instance.

It's very confusing behavior, and make it hard for me to have a sense
of what I've got open. It's extra confusing in a case like Treepad,
the type of program where it's normal to run multiple instances...

These two programs come to my mind first as examples, since I use them
daily. They are not at all the only programs with this buggy behavior.
Something going wrong with how the programmer wrote in their minimize
to tray option.

When I see an app listed as having a "minimize to tray" option in its
features list, my first reaction is to flinch. Due to the problems that
often accompany. (1) If the minimize to tray behavior is not optional,
it means the direct click on the minimize command is inconsistent with
the rest of my program windows. (2) It will be incompatible with my normal
min-to-tray command that is provided by my trayer utility. (3) It might
well be buggy, producing the double icon problem on its own.
Are you adapting? Or going in with a resource hacker?

I'd taken a quick look for that. I unpacked it, then opened it in Resource
Hacker. Unfortunately, there was nothing obvious there. I didn't spot
the buttons as easily replaceable resources. Instead, there were some
lines of embedded hex, for some pictures, which is probably where they
were drawn. Trying to modify that hex there, it's not within my experience.
The drawback for me is the fact that it doesn't work properly on a
maximised window. Since I'm having a closer look at it atm, I'm going
with the workround of stretching the window sideways and then upwards
but I'd much rather not have to.

Thanks for the heads up. I'd not tested it on many windows, in many states.
As is needed to really assess this type of program...
It doesn't feel like it uses much at all. I'm going to keep running it
for a while and see how it shapes up.

It probably does not do much of a discernible hit after initial launch.
What's valuable is to commit to the test of keeping it running for a while,
in order to gain confidence that it does not exhibit any leaky behavior.
Since you're volunteered to run the testing, I'll appreciate hearing how
you feel it shapes up.
IIRC Actual Title Buttons has recently gone freeware, and is a joke
compared to MME

I don't think I've used Actual Title Buttons, doesn't sound familiar. But
then from your comment, guess I'm not missing anything...
TWI doesn't miss very often. And of course, it can tray by hot key which
is nice. And it does millions of other stuff.

That's a good point; its min-to-tray op is only one of a great number of
available functions.
But I am slowly moving away from it *sob* since switching to RunFast as an
app launcher. The main problem with TWI is that it overwrites app specific
hot keys. This can be a real nuisance at times. It is odd how many hot keys
you can keep in your mind and know nothing about until in the relevant app
window... when you find you've assigned the combination to some obscure
task in TWI :-(

I have trouble remembering hot keys, so would not get into the difficulty
of managing large numbers. But I see the problem there. Then, to even try
to stop and use one of those utils that gives you an interface for your
assigned system hotkeys, it would not help. As it's not going to go over
and read TWI's private HKCU key, nor those of any other app. It's also
totally out of the question to try for a direct-read of those keys oneself:

[HKCU\Software\Wonderful Icon\Version 1.5\Hotkeys]

"HKey0001"=hex:00,00,64,00,00,00,00,00,00,00,00,00,00,00,00,00,01,00,00,00

It might not even be possible for TWI to be programmed to avoid overwrites.
Since I assume that for other apps that offer specific hotkeys within the
interface, they also, like TWI, store those settings in their private config
locales, and in their own way.

I haven't noticed there being any standard or tradition for apps to write
to some central part of the registry to record their individual (set within
the program) hotkey assignments. Absence of that, I suppose some anarchy
amongst apps is inevitable.

(Note - all the above is casual guesswork; I've not researched the subject.)
But it's still a superb app - I doubt it will ever be out of my sys
tray. AFAIK, all it does is load a reg file on launch - I doubt it uses
any resources just sitting in the tray.

I doubt it does too. On reg use - yes, there is its HKCU key. There was
also one isolated other key, in HKCR, for WONDPPET.DLL. I did not keep that
key, as it did not serve any purpose, isolated and near-empty as it was.
Or at least, I'd not yet learned of any intended purpose. The DLL seemed
to still get called into play fine, I believe, w/o that key. Btw, I do
like the intriguing description given for that DLL:

"Wonderful Icon Puppeteer (does some of the dirty work for TWI)"
 
Back
Top