Opened 16 years ago

Last modified 2 years ago

#1006 assigned bug

inconsistent behavior of Revert button in Backgrounds preflet — at Version 2

Reported by: wkornewald Owned by: korli
Priority: low Milestone: R1
Component: Preferences/Backgrounds Version: R1/pre-alpha1
Keywords: GCI2011 Cc: wkornewald, MaxLuebbe, ekam
Blocked By: Blocking:
Platform: All

Description (last modified by wkornewald)

Open the Backgrounds preflet, change something, click Apply. Result: you can't click on Revert, anymore.

Change History (2)

comment:1 by korli, 16 years ago

  • Revert lets you go back to the current workspace settings (even after having applied), and it's the good behavior.
  • I don't understand the second point.

in reply to:  1 comment:2 by wkornewald, 16 years ago

Description: modified (diff)

Replying to korli:

  • Revert lets you go back to the current workspace settings (even after having applied), and it's the good behavior.

In order to analyze the problem, I've been playing with the Screen preflet which has the same behavior and I agree that for preflets which have an Apply button Revert should go back to the currently active configuration. What irritated me was that right after having clicked Apply I didn't get a chance to revert to the configuration before I pressed Apply. I don't see why this should be prohibited.

If you make new changes after having clicked Apply the Revert button should only undo the new changes (like it already does).

BTW, R5 has similar behavior for Screen (only Backgrounds is an exception): Revert always brings you back to the state at program start (even after having pressed Apply). I've tested this scheme, too, but I think that the suggestion above is more intuitive. In case you want to test that behavior, I've committed my modified version of Screen (it can still be reverted).

At least, in R5 Backgrounds is not consistent with the other preflets, so I think we should fix that behavior. What do you think?

  • I don't understand the second point.

This is related to my suggestion above, but after having played around with the Screen preflet I think the second point is unnecessary and it's not worth the effort.

Note: See TracTickets for help on using tickets.