Re: Changing inactive behavior
Daniel Benamy <[email protected]>
| Newsgroups | gmane.comp.misc.workrave.user |
|---|---|
| Message-ID | <[email protected]> |
Joe Wells wrote: > Daniel Benamy <[email protected]> writes: >> it. I do have one problem- I want to pause the timers on inactivity, but >> they often reset while I'm reading a web page or something which doesn't >> involve typing or moving the mouse. I still have my hands at the >> keyboard so I still need to take a break and I'm missing them. I've seen >> some discussion of this issue [1] and would like to voice a me too. >> >> Some possible solutions: >> * Change the time workrave considers to be inactivity. On my install >> (1.9.1) it seems to wait about 7 seconds and then starts resetting the >> timers. I'd like to try that value at around 1 minute. > > There are some settings available in GConf that can affect this, but > it would be nice if there was a section in the ferences panel to > control them. And of course it would be great if this section had > proper help text that explained how they worked. I'm on windows 7. Is there a way to edit gconf settings on windows? A quick search didn't find anything. >> * Have the timers suspend when inactive like they do now, but not >> reset. > > Your idea is that the timers would only reset after counting down all > the way and _then_ going through the reset time? That is > interesting. I think that could be useful. I think that's it. When they count all the way down, the reset time is a break, right? >> * Have a separate option in the fs for resetting. This could be a >> binary switch or a configurable time. This lets people set things up the >> way they like at the cost of making the fs more complicated. I just subscribed and had to copy and paste from the archive into a new mail, so sorry if this shows up as a new thread in your mail client. Dan ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev