On 10/9/18 3:02 AM, Aurélien Pierre wrote:
But even if we keep the actual disposition, don't you think it's weird
that :
* in/out color profiles are stored in the color tabs, whereas they
are "basic" in the sense they are needed from technical
requirements and always on,
I don't think that's weird. The first place I'd look to change the
color profile is in the same tab with all of the other
color-behavior-changing tools. The fact that an input profile always
has to be be processed is an implementation detail. I don't think users
who are unacquainted with what's going on under the hood are going to
care about that.
* signal-processing modules are mixed with creative ones
The same applies here. I get the distinction you're making, but every
module is still a signal processor and is there in pursuit of a creative
goal.
The main problem I have with the current disposition is low-level
stuff comes last in the UI.
I grouse about that a bit sometimes as well, but my workflow has turned
out that 75% of what I process gets the same half-dozen low-level things
applied from a preset and then everything I actually need to adjust is
up top. The things I toggle and/or adjust frequently are favorites,
everything that's already in the pipe is under what's on and I go grab
the rarities from their tabs as I need them.
Maybe the way to solve that problem would be to have a switch to invert
the displayed order so the early-in-the-pipe stuff comes first.
There'd need to be some visual cue that it's being displayed that way,
but I'm not sure I'd want to devote the screen real estate to it.
--Mark
___________________________________________________________________________
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
