It might be worth adding a note in the manual, section 3.3.3 (History
stack) to that effect then.
On 2 October 2014 08:19, jeremy rosen <[email protected]> wrote:
> IIRC the history stack reflects the history i.e the order in which you did
> things on the image
>
> it's the order of the modules on the right container that reflect the
> order of the pipe (bottom to top)
>
> On Thu, Oct 2, 2014 at 6:09 AM, Colin Adams <[email protected]>
> wrote:
>
>> I ask, because I thought that you could not choose which order the
>> modules were processed, but I CAN choose which order they appear in the
>> history stack (crop-and-rotate vs. denoise profiled, for instance).
>>
>> I guess these are two different concepts, but I have been conflating them
>> in my mind.
>>
>>
>> ------------------------------------------------------------------------------
>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Darktable-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/darktable-users
>>
>>
>
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Darktable-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/darktable-users
