Re: [darktable-user] history stack still containing disabled modules after compression - why?

2018-01-31 Thread Sergii Dymchenko
For me having disabled modules in history is very useful, because the modules may have some non-default parameters set, and later I may want to re-enable them. For example, I can apply the watermark module, change some colors/position, export with the watermark. Later I can disable the watermark

Re: [darktable-user] Full path "Document Name" in EXIF on Flickr export

2017-04-18 Thread Sergii Dymchenko
uz.org> wrote: > Am Sonntag, 16. April 2017, 18:02:31 CEST schrieb Sergii Dymchenko: > > This "Document Name" is not present when exporting to file, only when > > exporting directly to Flickr. > > Could you check if that only happens when an image doesn't have a tit

Re: [darktable-user] Full path "Document Name" in EXIF on Flickr export

2017-04-16 Thread Sergii Dymchenko
This "Document Name" is not present when exporting to file, only when exporting directly to Flickr. And it's not possible to run exiftool in this case. On Sun, Apr 16, 2017 at 5:48 PM, <darkta...@911networks.com> wrote: > On Sun, 16 Apr 2017 17:03:31 -0700 > Sergii Dymche

[darktable-user] Full path "Document Name" in EXIF on Flickr export

2017-04-16 Thread Sergii Dymchenko
Hi, I noticed that when exporting to Flickr EXIF info of the exported JPEG has full path to the source file as "Document Name". I'd prefer not to expose this info, and there can be some (minor) security considerations (username on the local system can be revealed, for example). Is there an

[darktable-user] Image id in export file name

2017-04-15 Thread Sergii Dymchenko
Hello, I'd what to have a unique file name for every image in my library, that also can be traced back to the image in Darktable. I wanted to use "image id", but it's not a variable in the list of supported variables for export (although it supported in the watermarks module). Also, it looks