On Tue, Dec 17, 2013 at 5:51 PM, David Vincent-Jones
wrote:
> Combining the history and snapshots would be interesting. How about
> placing a "S" marker at one end of the History entry as a separate
> entity when a snapshot is taken,Then just clicking on the marker would
> display the snapshot tha
Combining the history and snapshots would be interesting. How about
placing a "S" marker at one end of the History entry as a separate
entity when a snapshot is taken,Then just clicking on the marker would
display the snapshot that is appropriate.
I also have had history losses (generally throu
Ok thanks for the feedback I have closed this pull-request!
--
Pascal Obry / Magny Les Hameaux (78)
The best way to travel is by means of imagination
http://v2p.fr.eu.org
http://www.obry.net
gpg --keyserver keys.gnupg.net --recv-key F949BD3B
---
pascal, please keep it post-1.4
that's the sort of stuff where we want heavy beta-testing before release to
see what's going on...
on the overall idea, I leave the actual discussions to those who know...
On Tue, Dec 17, 2013 at 3:38 PM, Pascal Obry wrote:
> 2013/12/17 Pascal Obry :
> > Lookin
Hallöchen!
Pascal Obry writes:
> Looking at the lens.c evolution it seems that this loose search has
> never been activated.
> Don't know why, but it seems to be working just fine in my case. We
> had many report about
> lens mis-match on the mailing-list, is there good reasons to not
> activate
2013/12/17 jeremy rosen :
> pascal, please keep it post-1.4
Sure. Marked as such on GitHub.
--
Pascal Obry / Magny Les Hameaux (78)
The best way to travel is by means of imagination
http://v2p.fr.eu.org
http://www.obry.net
gpg --keyserver keys.gnupg.net --recv-key F949BD3B
---
On Mon, 16 Dec 2013 13:40:23 +0100
Halgeir Kjønås Rennehvammen wrote:
> Denoise (profile) removes to much details for my taste so I have to use
> denoise (non local means) and the equalizer
> to get best results.
>
> To follow up the case further. The problem is on raw images from noisy
> came
2013/12/17 Pascal Obry :
> Looking at the lens.c evolution it seems that this loose search has
> never been activated.
> Don't know why, but it seems to be working just fine in my case. We
> had many report about
> lens mis-match on the mailing-list, is there good reasons to not
> activate this loo
Looking at the lens.c evolution it seems that this loose search has
never been activated.
Don't know why, but it seems to be working just fine in my case. We
had many report about
lens mis-match on the mailing-list, is there good reasons to not
activate this loose search?
If not, why not consider
My 2cents comment about it :
Personaly, i could like to see a gui merge of shapshot & history stack.
But i don't known if it's possible or difficult or ...
Regards
-- Message transféré --
From: Jose Carlos Garcia Sogo
To: "Per Östlund"
Cc: darktable-devel
Date: Tue, 17 Dec
On Tue, Dec 17, 2013 at 12:14 PM, Per Östlund wrote:
> It would also be nice to somehow couple the history to the snapshot
> feature. As it is I find the snapshot feature somewhat useless, since
> you have to remember yourself what the difference between the snapshots
> are. I think that has been
It would also be nice to somehow couple the history to the snapshot
feature. As it is I find the snapshot feature somewhat useless, since
you have to remember yourself what the difference between the snapshots
are. I think that has been mentioned before on this list. I'm not sure
what the best
On Tue, Dec 17, 2013 at 9:05 AM, Pascal Obry wrote:
>
> During a teaching session on dt a user got caught by this:
>
> - select a point in history (to watch the evolution)
> - leave darkroom and go to lighttable
>
> The dev history above the last selected point is lost.
>
> Looks like a dangerous
don't know about the purpose but I do like your idea
2013/12/17 Pascal Obry
> During a teaching session on dt a user got caught by this:
>
> - select a point in history (to watch the evolution)
> - leave darkroom and go to lighttable
>
> The dev history above the last selected point is lost.
>
During a teaching session on dt a user got caught by this:
- select a point in history (to watch the evolution)
- leave darkroom and go to lighttable
The dev history above the last selected point is lost.
Looks like a dangerous behavior to me. Has this been done on purpose?
My proposal would be
15 matches
Mail list logo
