(respond to myself)
After some discussion on irc with LebedevRI and houz, let's try to resume :
- This approach is overkilled, totally wrong, bad... so let's forget it
for now ;) (no problem, that's the goal of proposals)
- There is a problem with c (for devs, not for the user)
- It would be
Le dimanche 27 mars 2016 à 20:15 +0200, David Vincent-Jones a écrit :
> Current system works just fine for me
Sure but the proposal is targeted to developers. The crop module
is very hard to maintain. This has been discussed many times.
I've not looked at Aldric's proposal.
--
Pascal Obry /
Current system works just fine for me
David
On 27/03/16 08:03 PM, Alexander Rabtchevich wrote:
Hello
As an intensive darktable user from its beginning, I would say I got
used to the unified transformation tool it provides through crop and
rotate. Could the three different iops be combined
Hello
As an intensive darktable user from its beginning, I would say I got
used to the unified transformation tool it provides through crop and
rotate. Could the three different iops be combined into one collapsible
GUI item as it is now? If no, it could require precious vertical space,
Hi all,
As many of us , I'm tired of the "instability" of the clipping iop. Each
change is prone to a cascade of small other errors and/or subtle change
to the output... But that's not a secret for every dev who has hack this
file :D
So I thought about how to solve this situation. I came to
