On Mon, Oct 28, 2013 at 11:47 PM, Togan Muftuoglu <
tog...@users.sourceforge.net> wrote:
> > "Tobias" == Tobias Ellinghaus writes:
>
> Tobias> Hello everyone,
> Tobias> as you might have heard we are thinking about doing the next
> minor release
> Tobias> (1.4) in the not so dista
Hi all,
a quick update :
- tag collect is now integrated in the collect module, with tree display
of hierarchical tags
- keywords module has been move to the right panel and its "collect"
functionality has been dropped
Now it would be great to delete keyword module completely, but it still
has
not that i'm using tagging a lot, but i think what you say makes perfect
sense. so i'd vote to delete the keyword module and not allow that
reorganisation.
j.
On Tue, Oct 29, 2013 at 12:36 PM, AlicVB wrote:
> Hi all,
> a quick update :
> - tag collect is now integrated in the collect module, w
2013/10/29 AlicVB :
> Hi all,
> a quick update :
> - tag collect is now integrated in the collect module, with tree display
> of hierarchical tags
> - keywords module has been move to the right panel and its "collect"
> functionality has been dropped
Ok.
> Now it would be great to delete keyword
According to https://developer.gnome.org/glib/2.30/glib-I18N.html there is
a way to handle strings in enums and lists (use the N_() macro to define
them and then use gettext explicitly to display them in the UI, has anyone
tried this?
On Mon, Oct 28, 2013 at 8:53 PM, bartokk wrote:
>
> Il 28/ot
Am Dienstag, 29. Oktober 2013, 14:10:56 schrieb Dimitrios Psychogios:
> According to https://developer.gnome.org/glib/2.30/glib-I18N.html there is
> a way to handle strings in enums and lists (use the N_() macro to define
> them and then use gettext explicitly to display them in the UI, has anyone
Thanks for the explanation Tobias, I wasn't suggesting you don't know how
to use gettext at all :-). I just wasn't clear on what the limitation was,
and that is now perfectly explained as always, thanks.
On Tue, Oct 29, 2013 at 3:25 PM, Tobias Ellinghaus wrote:
> Am Dienstag, 29. Oktober 2013,
Rather than using the prescribed 'cmake' when up dating my git version:
cmake -DCMAKE_BUILD_TYPE=Release ..
I have been using the following in order to be able to directly import
images from my camera: cmake -DUSE_CAMERA_IMPORT=1
This option apparently is not working correctly. Can someb
Am Dienstag, 29. Oktober 2013, 19:11:09 schrieb David Vincent-Jones:
> Rather than using the prescribed 'cmake' when up dating my git version:
> cmake -DCMAKE_BUILD_TYPE=Release ..
>
> I have been using the following in order to be able to directly import
> images from my camera: cmake -DUS
Hi,
any details or steps to reproduce? RAW + XMP?
Ulrich
Am 29.10.2013 18:14, schrieb Togan Muftuoglu:
>
> Hi,
>
> I am using the git version 1.3-1235-g60ea384. When using the masks darktable
> crashed with the following message
>
> Error in `/usr/bin/darktable': free(): invalid next size (norma
> "Ulrich" == Ulrich Pegelow writes:
Ulrich> Hi,
Ulrich> any details or steps to reproduce? RAW + XMP?
It happenend as I was using the masks to draw an outline of a figure following
the contours of the body, so lots of clicks to define the path. The figure is
sitting man rougly one t
Am 29.10.2013 20:36, schrieb Togan Muftuoglu:
>> "Ulrich" == Ulrich Pegelow writes:
>
> Ulrich> Hi,
> Ulrich> any details or steps to reproduce? RAW + XMP?
>
> It happenend as I was using the masks to draw an outline of a figure following
> the contours of the body, so lots of clicks
> "Ulrich" == Ulrich Pegelow writes:
Ulrich> Am 29.10.2013 20:36, schrieb Togan Muftuoglu:
>>> "Ulrich" == Ulrich Pegelow writes:
>>
Ulrich> Hi,
Ulrich> any details or steps to reproduce? RAW + XMP?
>>
>> It happenend as I was using the masks to draw an outl
Hi all,
I ran through the profiling instructions posted at
http://www.darktable.org/2012/12/profiling-sensor-and-photon-noise/
for the Canon 70D. The generated tarball with the images and PDFs are
at https://drive.google.com/file/d/0B4xh3XYXDK_TYUtua2hfNUl3YVU/edit?usp=sharing
The presets are:
{
Oops, correction, the presets should be:
{"Canon EOS 70D iso 100", "Canon", "Canon EOS 70D",
100, {8.44345821677586e-06, 3.84995930291335e-06,
6.54462883339171e-06}, {6.79520904867053e-08, 5.06778223382642e-08,
6.35866223026098e-08}},
{"Canon EOS 70D iso 125", "Canon"
15 matches
Mail list logo