[Bug 103129] Re: Changing enabled status multiple times

2007-04-10 Thread Martin Pitt
Misunderstood you the first time. This is about changing state while synaptic is running. ** Changed in: restricted-manager (Ubuntu) Status: Needs Info = Confirmed -- Changing enabled status multiple times https://bugs.launchpad.net/bugs/103129 You received this bug notification because

[Bug 103129] Re: Changing enabled status multiple times

2007-04-10 Thread Martin Pitt
Fixed in bzr head. ** Changed in: restricted-manager (Ubuntu) Importance: Wishlist = Medium Status: Confirmed = Fix Committed -- Changing enabled status multiple times https://bugs.launchpad.net/bugs/103129 You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 103129] Re: Changing enabled status multiple times

2007-04-10 Thread Martin Pitt
restricted-manager (0.19) feisty; urgency=low . [ Martin Pitt ] * debian/control: Add X-Vcs-Bzr. * autostart/restricted-manager.desktop.in: Fix capitalization. (LP: #103248) * RestrictedManager/core.py: Keep track of whether a module's enable status has changed throughout

[Bug 103129] Re: Changing enabled status multiple times

2007-04-05 Thread Martin Pitt
Is there any particular reason why we should spend time for introducing inconveniences into programs? I never saw a Gnome program where an option could be toggled just once. What is the use case for that? ** Changed in: restricted-manager (Ubuntu) Importance: Undecided = Wishlist

[Bug 103129] Re: Changing enabled status multiple times

2007-04-05 Thread Torsten Spindler
The use case: 1) User enables restricted driver 2) Nothing happens until download or unconfiguration of driver starts 3) User clicks 'enable' again 4) A second window asking if to proceed appears, so two or more enable/disable actions are running parallel I find this behavior to be unintuitive

Re: [Bug 103129] Re: Changing enabled status multiple times

2007-04-05 Thread Martin Pitt
Hi, Torsten Spindler [2007-04-05 12:54 -]: 1) User enables restricted driver 2) Nothing happens until download or unconfiguration of driver starts 3) User clicks 'enable' again 4) A second window asking if to proceed appears, so two or more enable/disable actions are running parallel