D
Don Y
Guest
On 6/26/2023 3:01 PM, John S wrote:
How *often* do you do those?
Cookies? Breads? Pancakes? Bacon? Boiled egg?
There\'s nothing wrong with having a 9:59 *capability*. But, if
you have to specify the number of hours AND minutes, it\'s
wasted effort. Just like it would be wasted effort to have
to specify a cook time.
Or, to specify a cook temperature and time -- and have the
timer start NOW instead of when the oven gets up
to temperature.
Turn dial quickly. Software senses high rate of speed and increments
minutes in large steps. Carry-out of minutes field to hours. If
you overshoot, spin dial backwards. For finer selection, reduce rate
at which you turn dial.
Just like mouse motion.
This is more intuitive than \"select hours, press ENTER, select minutes,
press ENTER (and force seconds to be :00 -- even if you are editing time
that remains on a running timer!)\"
Specifying hours on microwave (timer) is just text entry -- type
something wider than xx:xx and you\'re specifying some number of hours
and xx:xx minutes:seconds.
On 6/26/2023 12:24 PM, Don Y wrote:
On 6/26/2023 5:52 AM, Liz Tuddenham wrote:
Don Y <blockedofcourse@foo.invalid> wrote:
[...]
If you can play music, then why can\'t you let ME decide what
music to play? Do you really think I am going to recognize one odd,
uniquely created tune vs. another in a single device? \"Is that
the song that tells me the oven is up to temperature
\"Steam heat\" from \"The Pyjama Game\".
-- or, that
the timer has expired?\"
\"Tick-Tock Tango\" played by Ray Martin & his Concert Orchestra.
It\'s a double-edged sword -- you want the user to decide what HE
thinks would be noticeable distinctions (based on whatever criteria
he\'s chosen). Yet, you don\'t want to burden him with having to
create \"ringtones\", audition them, install them, etc.
But, this is only necessitated by the increases in device complexity.
New oven has a general purpose timer. Lets you specify HOURS, *then*
minutes. How the hell often does someone specify an hour or more??
You ever cook a turkey? A roast? A roast chicken? A leg of lamb? Kielbasa and
sauerkraut? Baked potato? Slow cooking with a dutch oven?
To mention just a few.
How *often* do you do those?
Cookies? Breads? Pancakes? Bacon? Boiled egg?
There\'s nothing wrong with having a 9:59 *capability*. But, if
you have to specify the number of hours AND minutes, it\'s
wasted effort. Just like it would be wasted effort to have
to specify a cook time.
Or, to specify a cook temperature and time -- and have the
timer start NOW instead of when the oven gets up
to temperature.
Turn dial quickly. Software senses high rate of speed and increments
minutes in large steps. Carry-out of minutes field to hours. If
you overshoot, spin dial backwards. For finer selection, reduce rate
at which you turn dial.
Just like mouse motion.
This is more intuitive than \"select hours, press ENTER, select minutes,
press ENTER (and force seconds to be :00 -- even if you are editing time
that remains on a running timer!)\"
Specifying hours on microwave (timer) is just text entry -- type
something wider than xx:xx and you\'re specifying some number of hours
and xx:xx minutes:seconds.
(note that the *cook* timer is a separate beast -- for both ovens!)
when I hear an annunciator, how do I know if the first oven has
timed out? the second? or the general purpose timer? what if two
events occur in short order -- will the first be overwritten by
the second... because you opted to design with a SHARED display?
I\'ve not ye tried to let one timer preempt the \"song\" of an earlier
timer expiration. Can I actually TELL that two timers have expired??