Project

General

Profile

Feature #8727

Add toggle button to each level of the history stack

Added by Richard Wonka about 7 years ago.

Status:
Fixed
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
Start date:
06/01/2012
Due date:
% Done:

100%

Estimated time:
Affected Version:
System:
bitness:
64-bit
hardware architecture:
amd64/x86

Description

Add a toggle to each item in the history stack to enable/disable that item.

Effects of disabling an item in the stack:

  • preview changes: easy comparison for this item's effect on the image
  • [compress history stack] removes any disabled items
  • [create style] includes only enabled stack items

This toggle button could be a simple power-button icon as used in all modules.

~ as discussed earlier on IRC

History

#1 Updated by Richard Wonka about 7 years ago

[create style] behaviour might be better to set the default for style creation. The items still show up in the style creation dialogue, but they are unchecked by default.

#2 Updated by Richard Wonka about 7 years ago

Add to this an option to remove individual items in the stack.

#3 Updated by Simon Spannagel about 7 years ago

...and why not just using the power-button in the modules?

This feature would double the same functionality, just copying it to another place. I doubt that this will be realized/accepted.

#4 Updated by Ivan Tarozzi about 7 years ago

Simon Spannagel wrote:

...and why not just using the power-button in the modules?

This feature would double the same functionality, just copying it to another place. I doubt that this will be realized/accepted.

+1

We have to remember plugin (modules) are applied in the pipeline in a default order, not in activate order. So the same could be realized as Simon said. And eventually use the "preferred" or the "activated" panel (I/O and Star icons) to have a list of module to switch on/off.

#5 Updated by Richard Wonka about 7 years ago

Simon Spannagel wrote:

...and why not just using the power-button in the modules?

Because there is no way of switching a module on/off without the interface suddenly jumping around.
If I use the power buttons, then I have to deal with modules expanding on their own and have to scroll through the list of enabled and expanded modules to find the one that I was busy working with. (see #8644)

This issue here has only come up because of #8644 not being fixed.

Auto-expanding modules are quite a royal pain in the behind - and a major distraction from work. And there is a very viable solution as described in that issue.

#6 Updated by Ivan Tarozzi about 7 years ago

Richard Wonka wrote:

Simon Spannagel wrote:

...and why not just using the power-button in the modules?

Because there is no way of switching a module on/off without the interface suddenly jumping around.
If I use the power buttons, then I have to deal with modules expanding on their own and have to scroll through the list of enabled and expanded modules to find the one that I was busy working with. (see #8644)

This issue here has only come up because of #8644 not being fixed.

Auto-expanding modules are quite a royal pain in the behind - and a major distraction from work. And there is a very viable solution as described in that issue.

I agree! I found the solution to use module power-button (and favorite filter) useful because my panels doesn't move when selected.

I fixed issue#8644 hoping this helps :)

#7 Updated by Tobias Ellinghaus almost 7 years ago

  • % Done changed from 0 to 100
  • Status changed from New to Fixed

Since this was only asked for because modules used to expand when enabled I guess this can be closed – the power button behaves way better now. :)

Also available in: Atom PDF

Go to top