https://bugs.kde.org/show_bug.cgi?id=500146
cwo <cwo....@posteo.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cwo....@posteo.net
--- Comment #2 from cwo <cwo....@posteo.net> ---
(In reply to Nate Graham from comment #1)
> Is there any reason to expect you would remember the new thing you're
> proposing, though? Wouldn't it run into the same problem if you needing to
> remember to use it?
I think the idea is the following:
Situation: Time to get away from the computer for a bit, but need some
long-running task to continue in the mean time.
Current solution: Manually set inhibit. Come back later, computer is still on.
Continue working, hopefully remembering to turn the manual block off again.
Proposed solution: Manually set "inhitbit for 90 minutes". Come back later,
computer is still on (if it's earlier than 90 minutes), or sleeping (if it's
later). Resume as needed, no further invention is necessary.
In other words, in one case you need to remember two things (setting the block
and removing it), while in the other you only need to remember one. And the
first one is typically easy to remember, as it's something the user actually
wants to do, whereas the other is cleanup after the user has to after what they
want to do is complete. It's much easier to remember putting the original on
the photocopier if you want to make a copy than remembering to take it with you
when you have the copy you wanted.
This could be implemented with a timer combo box next to the "Manually Block"
button in the applet, similar to the one we have in kcm_powerdevil for choosing
the waiting time before sleeping etc. Like
[Manually block] [For 90 minutes |v]
[Manually block] [until unblocked |v]
Seems reasonable to me, and easy enough to understand. (Wording for the
indeterminate length case could be tweaked). Though if the user is regularly
compiling large projects it probably makes sense to integrate the building with
kde-inhibit so it automatically happens, but this is not something we can do
for the user, they have to set it up for themselves.
--
You are receiving this mail because:
You are watching all bug changes.
