Bug#295795: capplets: typing monitor ignores "Allow postponing of break" option

[Julian Gilbey]

On Sun, Feb 20, 2005 at 01:19:16AM +0100, Lo?c Minier wrote:
>         Hi,
> 
> On Fri, Feb 18, 2005, Julian Gilbey wrote:
> > I didn't try "closing it and restarting it" - it used to be that I
> > could change the preferences while it was running and it would respect
> > my new preferences without closing and restarting, whereas now it
> > requires closing and restarting.
> 
>  Yes I wanted to demonstrate starting the program without changing the
>  preferences too, hence I tested two times.
> 
> > >  Can you give detailed instructions on how to get the bug?  I need to
> > >  be able to reproduce it.
> > Run the program, change the preferences and wait for it to go into
> > typing break mode.  (You probably want to set a short Work interval
> > and Break interval, then restart before doing this!)  Has it respected
> > the postpone option if you change it while the applet is running (not
> > while it is in break mode ;) ?  It doesn't for me (but used to).
> 
>  This is exactly what I did:
>  - open xterm,
>  - launch gnome-typing-monitor,
>  - right click on its icon in the notification area,
>  - select preferences,
>  - click on "lock screen to force a pause",
>    (note that at this point the program has "allow postponing a break"
>    already selected since it's the setting I used last time)
>  - type for some time,
>  - I got the "make a break" screen locking, and postponed,
>  - click on close,
>  - type for some time,
>  - I got the "make a break" screen locking, and postponed,
>  - right click on its icon in the notification area,
>  - select preferences,
>  - removed that option to allow postponing breaks,
>  - type for some time,
>  - I got the "make a break" screen locking, and couldn't postpone.
> 
>  Could you try reproducing the above and tell me when you do not have
>  the same results anymore?

That's really weird: I've just tried doing the same as you described
and it worked perfectly.  The bug seems to have vanished.  Let's close
this bug report and I'll reopen it if the behaviour appears again, OK?

   Julian