Basic use of History Stack and Active Modules panel

I am new to dt (5.2.0) and I would like to get help on History Stack (HS) and Active Modules button
Here are some behaviour I have experienced, I would like to get feedback or amendment.

1
Compress HS button truncates the HS above the item currently selected, consolidating all the instances of a given module in just one. Holding Ctl when clicking the button skips this consolidation

2
When editing a module in Active Modules panel, HS auto-truncates all the items above the selected one (if any) without even warning the user

3
Clicking the Active Modules alternatively shows :
a) active modules (the ones in the pipeline) for the current image

b) a much longer list of modules (all of them?)

4
Nothing happens when right clicking the Active Modules button (doc says HS should show up, including not actually active ones)

5
If, while testing an image, a few active modules are switched off, their “reactivation” requires the user to remember their names. Or browse the HS to spot them
No way to recall modules that the user has altered away from its default state.

Thanks

The feature you refer to of show all history modules works for me in DT5.3 on Windows. If this feature is not working for your version of DT please let us know the OS you are using.

1 Like

thanks,

Left-clickng and hovering on Active Modules buttons shows only one tip:
show only active modules, although the view really cycles between only active modules (switch button highlighted) and many more modules (switch button on or off, presumably all modules)

Right-clicking on the button nothing happens (visible modules don’t change), but the tip cycles between
show only active modules
show all history modules

I can’t see DT 5.3 in install | darktable for windows, only 5.2

My OS is Windows 11 Home version 24H2 build 26100.4652 installed 6 dec 2024

5.3 is a development version.

You can find downloads around the forum.

1 Like

thats intentional

also intentional to be able to continue at an earlier step in the history stack

also intended

depends on your history stack - if it contains inactive modules then you can display them conditionally aso in the list of active modules.

instances must be created explicitly and then be named. In general changes overwrites the settings but the history stack is aware of older settings.But don’t forget #2: if you change settings on an older history entry you’ll lose all later edits.

maybe you should consult the manual to learn about darktable: https://darktable-org.github.io/dtdocs/en/
at least: darktable user manual - an introduction to darktable's workflow and darktable user manual - the pixelpipe

1 Like

I mention I am on windows 5.3 in case this problem is specific to 5.2 or your operating system. Stick with 5.2 stable release. I just run the development version looking out for bugs that the developers need to know about.

yes, you can click once extra on all the tabs, except the left QAP, to get a list of (nearly) all modules. Click once more to revert to limited list.