KJ wrote in bug #158:
I have a micropause with a restbreak iminent. Hence I'm getting a restbreak
prelude. I continue working, effectively postponing the restbreak (and the
micropause, which should not be possible by my settings).

I'm not sure what to do about the micropause-that-shouldn't-be-postponed. It's
an awkward situation...

I'm wondering... Is this a duplicate of bug 47?

I have the same problem. When I get a micropause, I don't want to ignore it, but when I press the restbreak button and in the restbreak screen I say I want to continue, then I haven't had my micropause. 

A feature request: Is there a possibility to have a setting in the general settings to say you don't want the restbreak button in the micropause screen? Then I really can't ignore the micropause: The micropause is in my situation more important then the restbreak.

Weird. You're right (at least for WR 1.9.0, as installed on my ubuntu 9.04).

It used to be so that when you click the "postpone" or "skip" button in this case, the micropause window would re-appear.

I'm not sure what happened to that functionality.

Kees-Jan,

Are you one of the developers of Workrave? Are the developers of workrave reading this issue? This because of the fact that the initial note is from november 2002..

No, I am not. My contribution to workrave is more in the area of generating bug reports, rather than fixing them :-) Rob (who posted the original note) is a workrave developer, and he receives a mail of every change of every bug (as do a number of other people).

On the other hand, Workrave is developed/maintained by volunteers, this is hardly a critical issue, and it has been quite sunny lately. Priorities are likely to be elsewhere :-)

Re-enabled functionality mentioned in comment #3

(commit a73d611e305568b6871280d544b515a3152243a0)

When a restbreak is started instead of a microbreak (because a restbreak is due within 30 seconds after the microbreak), the restbreak is now started with the 'maximum number of prompts' of the microbreak if this is smaller than the 'maximum number of prompts' of the restbreak. This should make it impossible to postpone a microbreak if the microbreak is configured that way. 

Perhaps the prelude text should be changed to "it's time for you microbreak and restbreak"... Ideas?

(In reply to comment #7)

I wouldn't over-complicate things. Using the smallest "maximum number of prompts" sounds perfect. I'll be presented with a restbreak window. I could, of course, click "postpone", but that should give me a microbreak window (which doesn't have skip/postpone in my case). So there's no escaping my microbreak and all is well with the world.

Of course, there may be purist expecting more preludes before being forced to take a (rest)break, but most people won't be counting, and a dedicated "it's time for your microbreak and restbreak" prelude seems way over the top.