I really don't understand this confusion. (Apart from the fact that
some people did not seem to realise that 'perspective correction' is a
separate module, different from the keystone adjustment in the crop
module.)
In all the modules, the effects of the current setting are visible
immediately;
* DougC [12-08-20 19:33]:
> My question comes from a thread here on Perspective correction where it was
> said:
>
> Leaving
> (closing) the module finalizes the changes.
>
>
>
>
>
>
> On Tue, 08 Dec 2020 18:45:50 -0500 Stéphane Gourichon
> wrote
>
>
> Most
My question comes from a thread here on Perspective correction where it was
said:
Leaving
(closing) the module finalizes the changes.
On Tue, 08 Dec 2020 18:45:50 -0500 Stéphane Gourichon
wrote
Most modules get their effect applied continuously as you set the
Most modules get their effect applied continuously as you set the
parameters, they don't need you to leave them.
Can you provide examples of modules that actually need you to leave them
to finalize the operation ?
Regarding "crop and rotate", to finalize a crop I double-click inside
the
Hi Doug,
I know from the crop module that if you click at the top of the module
near the name the crop event is finalised. I presume other modules will
work the same.
On Wed, 9 Dec 2020 at 09:16, DougC wrote:
> I am puzzled why the act of leaving a module is used as an event to
> activate
I am puzzled why the act of leaving a module is used as an event to activate or
finalize the operation of the module. This seems like a strange user interface
practice. Can someone enlighten me as to how and why it was adopted in
darktable?
