>
>
>
> * or you want to temporarly disable some module to do some work (working
> in colors before applying the monochrome module to help visualize what's
> happening) I can understand that use-case, but you should do that by
> disabling/enabling the module (again, the active module tag is probably the
> way to go. I personally have a shortcut to toggle the monochrome module
> just for that purpose)
> Again, inserting in history is not what you want here.
>
Interesting. I think this is what I was looking for, I haven't though into
using shortcuts for this. Highly appreciated a new perspective :)
Anocha, noup. I wasn't proposing anything to be honest; just waiting for an
answer that could give me a different perspective on how to interact better
with my history stack, which Jeremy just did. As i said, sometimes we ask
for features that are already there but we don't know how to use. Is just a
matter of learn and get a different perspective.
--
tatica
Maria Gracia Leandro
Blog: http://tatica.org
Portfolio: http://tap.tatica.org
LinuxUser= 440285 GPG Public Key: E1CDCC56
------------------------------------------------------------------------------
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
_______________________________________________
Darktable-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/darktable-users
