Re: [darktable-user] ATTENTION: darktable master may go unstable.

2019-03-07 Thread jys
On Thu, Mar 7, 2019, at 22:55, Pascal Obry wrote: > Le vendredi 08 mars 2019 à 01:30 -0500, jys a écrit : > > I also noticed that the lens correction module now also allows > > multiple instances, so there's potential for awesome here. > > I don't see this here. You're right... the menu is

Re: [darktable-user] ATTENTION: darktable master may go unstable.

2019-03-07 Thread Pascal Obry
Le vendredi 08 mars 2019 à 01:30 -0500, jys a écrit : > I also noticed that the lens correction module now also allows > multiple instances, so there's potential for awesome here. I don't see this here. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of

Re: [darktable-user] ATTENTION: darktable master may go unstable.

2019-03-07 Thread jys
On Thu, Mar 7, 2019, at 13:28, Edgardo Hoszowski wrote: > Modules can now be moved pretty much everywhere (with shift + drag) Well, this is a fine can of worms! :D This is probably the only thing that would have gotten me to start building dt from master instead of stable, since I depend on

Re: [darktable-user] ATTENTION: darktable master may go unstable.

2019-03-07 Thread Edgardo Hoszowski
So everybody is in the same page, a few notes: Modules can now be moved pretty much everywhere (with shift + drag), if not, the system will not allow it (i.e. RAW modules can't be mixed with Lab/RGB modules) The only exception is: Lab modules can't be before input color profile or after output

[darktable-user] Re: [darktable-dev] ATTENTION: darktable master may go unstable.

2019-03-07 Thread Pascal Obry
Le jeudi 07 mars 2019 à 22:16 +0100, Moritz Moeller a écrit : > Fucking amazing!!! So next DT will get a node editor? :] > Let me know when this is merged, I want to try this immediately! It is now merged. Do report all issues on GitHub. Thanks, -- Pascal Obry / Magny Les Hameaux (78)

[darktable-user] ATTENTION: darktable master may go unstable.

2019-03-07 Thread Pascal Obry
ATTENTION: darktable master may go unstable. I'm about to merge a commit in master that could make darktable unstable. This is an extensive change from Edgardoh which adds: - mask history (that is a mask is now part of the history and when changed will not change the same mask in the same