Bug 152 - collective: break window strangeness
Status:
RESOLVED FIXED
Component:
Core
Version:
1.0.0
Hardware:
PC Linux
Importance:
P3 normal
Target Milestone:
---
Assignee:
Rob Caelers
URL:
Depends on:
Blocks:
Reported:
Nov 10 2002 08:06:21 UTC
by:
Kees-Jan Dijkzeul
Modified:
Nov 11 2002 09:44:10 UTC
WhoWhenWhatRemovedAdded
Rob CaelersNov 10 2002 09:38:01 UTCstatusNEWASSIGNED
Rob CaelersNov 10 2002 13:03:27 UTCresolutionFIXED
statusASSIGNEDRESOLVED
Kees-Jan DijkzeulNov 11 2002 02:54:13 UTCstatusRESOLVEDREOPENED
resolutionFIXED
Rob CaelersNov 11 2002 09:22:47 UTCstatusREOPENEDASSIGNED
Rob CaelersNov 11 2002 09:44:10 UTCresolutionFIXED
statusASSIGNEDRESOLVED
Description
Kees-Jan Dijkzeul  Nov 10 2002 08:06:21 UTC
When one instance of workrave tells me to break, and I run to another computer
(well, actually, an x-server), there is no break window there (I expect one to
be there).

Then, when I start working, all of a sudden, a break window appears. At the very
least, I expect a prelude at this point.
Comment 1
Kees-Jan Dijkzeul  Nov 10 2002 08:26:08 UTC
It gets even worse

The break window that appears may show a remaining break time that is different
(larger, sometimes even 10 minutes) from the time on the other computer.

Also, the clock may not be running, i.e. the remaining break time doesn't get
any less.
Comment 2
Rob Caelers  Nov 10 2002 09:38:01 UTC
> When one instance of workrave tells me to break, and I run to another computer
> (well, actually, an x-server), there is no break window there (I expect one to
> be there).

No.

> Then, when I start working, all of a sudden, a break window appears. At the 
> very least, I expect a prelude at this point.

When you move from computer A to B and start working on B, the current state is
retrieved from A and restored on B. If you have a break window active on A, a
break window will be shown on B. If the 2nd prelude was active on A, then B will
show the 2nd prelude window.

>The break window that appears may show a remaining break time that is different
>(larger, sometimes even 10 minutes) from the time on the other computer.

Strange, do you have a log files of both workraves?

>Also, the clock may not be running, i.e. the remaining break time doesn't get
>any less.

Are you active on the computer that shows the window?
Comment 3
Rob Caelers  Nov 10 2002 13:03:27 UTC
This bug is related to bug #155. An disabled timer could not be frozen. So the
idle time was immediatly reset.
Comment 4
Kees-Jan Dijkzeul  Nov 11 2002 02:54:13 UTC
I understand your explanation of the design and your reasoning behind it. I just
don't like the resulting behaviour. Showing a break window is pretty intrusive.
All of a sudden, I'm blocked from working. This should not happen to me (or my
collegues accidentally using the computer), without proper warning. Hence the
requirement that a break window should _never_ be shown without a prelude first.

Hence, there are two options: Either the break window should already be there,
or you should show an additional prelude before displaying the break window.

(thanks for fixing the timer, though :-)
Comment 5
Rob Caelers  Nov 11 2002 09:22:47 UTC
Ok, an active break window now turns up as a final prelude window on the other
computer.