Re: [darktable-user] Leaving a module to conplete an operation?

[KOVÁCS István]

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; is that not the case? Leaving the module only means that
you hide adjustment options for the modules' parameters and turn off
any mask display if currently shown (and, in case of crop and
perspective correction, you also hide the area that's outside the
selected crop rectangle, because it'd be a waste of screen estate to
show them).
For crop and perspective adjustment, the crop rectangle is visible
while you adjust the module's parameters, highlighting the part that
will be kept when you leave. When you close the module, the area
outside said rectangle is hidden, but no data is actually discarded;
you can always to back and adjust the parameters (crop, rotation etc.)
as you wish.
With crop, there's the keystone tool, which is a bit special in that
it requires you to click OK to 'commit' the adjustments. If the image
was continuously updated (applying the parameters set by dragging the
control points immediately), the control points *themselves* would be
moving all the time, which would make editing a nightmare.

Kofa

darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org

Re: [darktable-user] Leaving a module to conplete an operation?

[Patrick Shanahan]

* 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 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 ?

afaik, "perspective corrections" is the only module which requires leaving
to finalize an action.


-- 
(paka)Patrick Shanahan   Plainfield, Indiana, USA  @ptilopteri
http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri
Photos: http://wahoo.no-ip.org/piwigo   paka @ IRCnet freenode

darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org

Re: [darktable-user] Leaving a module to conplete an operation?

[DougC]

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
  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 ?

darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org

Re: [darktable-user] Leaving a module to conplete an operation?

[Stéphane Gourichon]

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 cropped area. "Folding" the module by clicking on its name in the 
right panel also works.


It kind of makes sense to consider a crop has to be confirmed, although 
since that was coded, darktable gained "undo" ability with ctrl-z.



From https://www.darktable.org/usermanual/en/modules.html :

> When you are done and want to execute the crop, just give focus to 
another module or double-click into the image base.



--
Stéphane Gourichon



Le 08/12/2020 à 23.36, Terry Pinfold a écrit :

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 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?





darktable user mailing list to unsubscribe send a mail to
darktable-user+unsubscr...@lists.darktable.org




--
Dr Terry Pinfold
Cytometry & Histology Lab Manager
Lecturer in Flow Cytometry
University of Tasmania
17 Liverpool St, Hobart, 7000
Ph 6226 4846 or 0408 699053


 
darktable user mailing list to unsubscribe send a mail to 
darktable-user+unsubscr...@lists.darktable.org




darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org

Re: [darktable-user] Leaving a module to conplete an operation?

[Terry Pinfold]

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 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?
>
>
>
>
> 
> darktable user mailing list to unsubscribe send a mail to
> darktable-user+unsubscr...@lists.darktable.org
>


-- 
Dr Terry Pinfold
Cytometry & Histology Lab Manager
Lecturer in Flow Cytometry
University of Tasmania
17 Liverpool St, Hobart, 7000
Ph 6226 4846 or 0408 699053


darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org

[darktable-user] Leaving a module to conplete an operation?

[DougC]

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?

darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org