Hi Diederik,
There was a missing reset=1 / reset=0 pair around the gui_init() call
to the format plug-ins. Your message put me on the track.
This is now fixed.
--
Pascal Obry / Magny Les Hameaux (78)
The best way to travel is by means of imagination
http://www.obry.net
gpg
Hi Diederik!
Well, this is what I see every start. System: Debian 10, I tried
starting with empty profile. Will you remove that single line of code?
Thanks for quick reply,
Timur.
On Mon, 2019-11-18 at 21:23 +, Diederik ter Rahe wrote:
> Hi Timur, Pascal,
>
> I used to see this when I was
https://github.com/darktable-org/darktable/issues/3435 — this issue can
be closed, was fixed by
https://github.com/darktable-org/darktable/commit/d4156db4a3ebc8df7f872eb04bcef6530a2f4f70
Thanks a lot!
Timur.
On Sat, 2019-11-16 at 17:33 +0300, Timur Irikovich Davletshin wrote:
> Christian,
Le lundi 18 novembre 2019 à 20:13 +0100, Aurélien Pierre a écrit :
> Don't, it's fine.
>
> But serious bug reports like crashes, regressions, Mac/Win/Nux and
> CPU/GPU inconsistencies do pile up faster than fixes, so all the
> cosmetic talk about the proper way to write grey is kind of
>
Don't, it's fine.
But serious bug reports like crashes, regressions, Mac/Win/Nux and
CPU/GPU inconsistencies do pile up faster than fixes, so all the
cosmetic talk about the proper way to write grey is kind of hilarious. I
wonder sometimes if users realize we are just a handful working on a
Hi Timur,
> What is the point of giving user notification on dt start about TIFF
> compression level?
No point. That's a side effect of the toast being displayed when
changing module sliders from a key without opening the module.
Some of this has already been fixed by Diederik (in CC).
There
My apologies
On Mon, Nov 18, 2019 at 10:58 AM Aurélien Pierre
wrote:
> Forget about segfaults and crashes, our first priority is now to make
> every native English speaker feel respected in his difference and identity,
> offering fully differentiated support of every English dialect : en_GB,
>
Hi there!
A simple proposal from photographers point of view:
There is a tip tool when editing BASE CURVE points with a mouse, which
says; abcissa: input, ordinate: output etc
THAT is useless! Instead SHOW x and y VALUES, when moving a point with a
mouse! That would be very useful, for
Forget about segfaults and crashes, our first priority is now to make
every native English speaker feel respected in his difference and
identity, offering fully differentiated support of every English dialect
: en_GB, en_AU, en_US, en_ZA, en_CA, en_NZ, en_FJ…
Meanwhile, people speaking languages
No, dt will say that you're importing 400 files, but in fact 200 will
be imported.
Timur.
On Mon, 2019-11-18 at 10:36 -0500, Julian Rickards wrote:
> Perhaps: 200 RAW (200 JPG, ignored)
>
___
darktable developer mailing
Perhaps: 200 RAW (200 JPG, ignored)
On Mon, Nov 18, 2019 at 9:41 AM Timur Irikovich Davletshin <
timur.davlets...@gmail.com> wrote:
> Well, I agree it's not a big deal. But if one shoots (just as example)
> raw+jpeg and then tries to import only raw files... — he will get
> message of
-- Tongue firmly in cheek --
en-GB or en-US ?
That is the real question.
They are two very different languages, at present darktable seems to
assume they are the same!
R.
On 18/11/2019 14:36, Julian Rickards wrote:
grAy is the American spelling and there's nothing wrong with that
(despite
Well, my point was not about American vs British. It was just an
example of inconsistency. And odd tradition of lowercasing all capitals
make it only worse. Regarding this particular case... Well I think this
information (colorspace, type of curve) somehow must be delivered to
user. Otherwise
grAy is the American spelling and there's nothing wrong with that (despite
being a Canadian and using British spelling, LoL) but Timur is correct,
there should be consistency and, in addition to sticking to the same
spelling of gray/grey, I think that that the English version of the
documentation
Maybe it's time to choose project leader and start collecting
donations?
On Mon, 2019-11-18 at 15:11 +0100, Aurélien Pierre wrote:
> darktable also lacks a board of investors, a CTO, a head of UX, a
> project management, a panel of test users, a famous photographer as a
> brand ambassador, many
darktable also lacks a board of investors, a CTO, a head of UX, a
project management, a panel of test users, a famous photographer as a
brand ambassador, many tracking features to collect statistics on usage
"to improve the performance", an annual coding sprint in the Bahamas and
a couple of
Well, that’s the problem with basic adjustment module - IMHO it shouldn’t
exist, because it duplicates functionality of other modules, while adding
problems like the one discussed here.
> On 18 Nov 2019, at 16:13, Moritz Moeller wrote:
>
> On 15.11.19 12:02, parafin wrote:
>> I think these
Actually I agree. Darktable lacks of terminology unification across
modules. E.g. AFAIR there are around 6 different names for 18% gray. In
some places it is "grey" but in others it is "gray".
Timur.
On Mon, 2019-11-18 at 14:03 +0100, Moritz Moeller wrote:
> On 15.11.19 12:02, parafin wrote:
> >
On 15.11.19 12:02, parafin wrote:
I think these numbers don't have units, so why do expect them to mean
the same thing in different modules, even if we ignore the pipe order?
Because that's the most basic requirement of usability. That things
named the same way act the same way and mean the
And if that is what the issue is (the extra file extension component in the
filename), I am pretty sure I addressed that in my video.
A simple rename routine to remove that from your xmp files will sort it out.
Cheers,
Bruce Williams.
-- Forwarded message -
From: Bernhard
Date:
20 matches
Mail list logo
