Re: [darktable-dev] Add Location data to exported jpeg files
I believe that any image that has a geotag in Darktable has it included when the image is exported as a JPEG. Are you sure the geotags are being properly applied to your images within Darktable (i.e., are the "latitude" and "longitude" fields in the "image information" panel populated)? -- August Schwerdfeger aug...@schwerdfeger.name On 7/26/23 08:45, Ramnarayan.K wrote: Hi I primarily show in NEF (raw) on a camera that does not have Location / GPS data functions. I upload a lot of images to inaturalist.org <http://inaturalist.org> where the observations (pictures) are usually geo-referenced. Currently I end up manually adding locations. Most of my locations are standard (fixed) for significant number of exported images. I was wondering how I could enable geo-referencing of my exported images. * * *# What I tried so far :* 1. I created a gpx file (created a google earth location and exported to KML and then used a kml to gpx converter) 2. I applied this GPX file to the geotagging menu options However the exported files emerge without any geotags Kindly advise, thanks Ram ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Import from camera/ memory card: some probleems
The thumbnails do not show up when importing from a folder, only when importing from a device using the 'gphoto2' library. If you see only two buttons in the import module (and not the "scan for devices" button) then your copy of Darktable was not compiled with 'gphoto2' support. I would not recommend using folder import for images on an SD card: if you import such images and do not promptly move them *off* the SD card, you will lose access to them as soon as the card is unmounted. -- August Schwerdfeger aug...@schwerdfeger.name On Wed, Jan 6, 2021 at 10:42 AM Peter Harde wrote: > Hi Laurent, > > ok, thank you for clarification. But I'm afraid I still don't really > understand how you get thumbnails into the import dialog. The import > module of lighttable (dt 3.4.0) has two buttons, "image..." to import > imag(es) and "folder" to import the content of a folder (optional > recursive). > > I assume your card reader is mounted as linux block device. Clicking > "folder" you should get a file selector (dialog) like the one shown in > the attached screenshot. For me this dialog appears with a file list, > with small leading symbolic icons (no thumbnails). And building the > content of the dialog is extremely fast. I cannot find a way to get > thumbnails into this dialog... > > Peter > > Am 06.01.21 um 15:56 schrieb Laurent Zimmermann: > > Hi Peter, > > > > > > Sorry that I was not clear. > > > > I meant the thumbnails that appear in the window opened in darktable > > if I click on "Import from camera" (although just an USB3 card reader > > with my CF is connected, not the camera itself, which is only USB2). > > > > I suggested that THESE thumbnails (not those of the lighttable) could > > (also) be saved in a cache. > > > > About the file list, I am almost certain I saw it once (and only once) > > instead of the thumbnails, but I never was able to reproduce. > > > > I spoke about Dolphin only for speed comparison. > > > > Following you suggestion I gave dt 3.4.0 a try, but on my Windows > > computer. With 3.4 (under Windows), the import from a card reader no > > more copies the files to the hard disk as 3.2.1 did (under Linux). And > > if I connect my camera, dt recognizes it but says it is busy. Sorry > > for mixing the OS's. > > I've found the Zadig tool to change the driver, but it had no effect, > > at least for the card reader (not yet tested with the camera, but it > > is USB 2 only). > > > > > > Thanks, > > Laurent > > ___ > darktable developer mailing list > to unsubscribe send a mail to > darktable-dev+unsubscr...@lists.darktable.org ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Scan for devices option is not available
The absence of the "scan for devices" button itself, as opposed to an import button for the specific camera, suggests that your Darktable install was compiled without access to 'gphoto2'. If you compiled Darktable yourself, make sure the 'libgphoto2-dev' package is installed and look over the build logs -- there should be a line telling whether or not 'gphoto2' was found in usable form. If you installed it from a package, it is most likely a problem for the people who assembled that package, rather than for the Darktable developers themselves. -- August Schwerdfeger aug...@schwerdfeger.name On 11/11/20 11:59 PM, Patrick Shanahan wrote: > * rob lineberger [11-11-20 23:37]: >> I've heard great things and I can't wait to try tethering my Canon 7D with >> darktable. However, there is no menu option for "Scan for Devices." Or >> "import from camera", or "tethered shoot" for that matter. >> >> I'm on Ubuntu 18.04.5 LTS with a fresh install of darktable 3.2.1. I am in >> lightroom mode. As you can see from the screenshot below, there are only >> two options under the import menu: Image and folder. >> >> I am 100% certain that my camera is supported, it works, the cable works, >> and the OS does not have the camera locked. libgphoto2 is installed and >> functional. When I check the terminal output I see these messages: >> >> (darktable:23709): GLib-GObject-CRITICAL **: 23:33:07.125: >> g_object_set_data: assertion 'G_IS_OBJECT (object)' failed >> >> (darktable:23709): Gtk-CRITICAL **: 23:33:07.125: >> gtk_widget_get_has_tooltip: assertion 'GTK_IS_WIDGET (widget)' failed >> >> Without knowing how darktable works this is as far as my knowledge can take >> me so I hope someone out there knows what is going on so I can start >> snapping breathtaking tethered shots. Thanks! >> >> missing scan option > so your system has not made your camera available to darktable or > darktable is broken which would indicate the need for an issue report at > https://github.com/darktable-org/darktable/issues/new/choose > > ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Issue building manual after OS upgrade
I ran into this problem in a different context, and the cause turned out to be that the 'JAVA_HOME' environment variable was not set how I expected, causing 'fop' to use the wrong JRE. -- August Schwerdfeger aug...@schwerdfeger.name On Sat, Aug 29, 2020, 04:32 Peter Harde wrote: > Dear developers, > > after upgrading Ubuntu 18.04 to 20.04 it is no longer possible to build > the manual. Using the command "make darktable-usermanual" I get this > messages : > > ... [100%] Building usermanual > Making portrait pages on A4 paper (210mmx297mm) > [warning] /usr/bin/fop: Unable to locate avalon-framework in > /usr/share/java > Exception in thread "main" java.lang.NoSuchMethodError: > java.nio.CharBuffer.limit(I)Ljava/nio/CharBuffer; > at org.apache.fop.fo.FOText.characters(FOText.java:143) > at org.apache.fop.fo.FObjMixed.characters(FObjMixed.java:74) > at > org.apache.fop.fo > .FOTreeBuilder$MainFOHandler.characters(FOTreeBuilder.java:390) > at > org.apache.fop.fo.FOTreeBuilder.characters(FOTreeBuilder.java:136) > at > > org.apache.xalan.transformer.TransformerIdentityImpl.characters(TransformerIdentityImpl.java:1126) > at > org.apache.xerces.parsers.AbstractSAXParser.characters(Unknown Source) > at > org.apache.xerces.xinclude.XIncludeHandler.characters(Unknown Source) > at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanContent(Unknown > Source) > at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown > > Source) > at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown > Source) > at org.apache.xerces.parsers.XML11Configuration.parse(Unknown > Source) > at org.apache.xerces.parsers.XML11Configuration.parse(Unknown > Source) > at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) > at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown > Source) > at > org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) > at > > org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:485) > at > org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:293) > at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:116) > at org.apache.fop.cli.Main.startFOP(Main.java:183) > at org.apache.fop.cli.Main.main(Main.java:214) > make[3]: *** > [doc/usermanual/CMakeFiles/darktable-usermanual.dir/build.make:62: > doc/usermanual/darktable-usermanual.pdf] Fehler 1 ... > > I tried with Java-11 (openjdk 11.0.8+10-0ubuntu1~20.04) but that makes > no difference. Is someone able to help ? The build of dt is running > without any problem. > > Best regards > > Peter Harde > ___ > darktable developer mailing list > to unsubscribe send a mail to > darktable-dev+unsubscr...@lists.darktable.org > > ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] 3.0.2 for Mac wont start: file system relative paths not allowed in hardened programs
Darktable starts normally from the DMG. -- August Schwerdfeger aug...@schwerdfeger.name On Thu, Jul 2, 2020 at 4:05 AM Moritz Moeller wrote: > I'm running 3.0.2. on 10.15.5 w/o any issues since that DT version was > released. > Not sure though when I upgraded from 10.15.4. Maybe I had 3.0.2 already > installed by then. > > .mm > > ___ > darktable developer mailing list > to unsubscribe send a mail to > darktable-dev+unsubscr...@lists.darktable.org > > ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] 3.0.2 for Mac wont start: file system relative paths not allowed in hardened programs
I have no problem running Darktable 3.0.2 on macOS 10.15.5. -- August Schwerdfeger aug...@schwerdfeger.name On Wed, Jul 1, 2020 at 2:39 PM parafin wrote: > That's how app bundles work, so I'm not sure how it can be forbidden. > But maybe it wants @rpath, not @executable_path... Is it reproducible by > anyone else? I don't have 10.15 macOS here. > > > On Wed, 1 Jul 2020 09:08:35 -1000 > Ken Ellinwood wrote: > > > $ ls -l > > > /Applications/darktable.app/Contents/MacOS/../Resources/lib/libepoxy.0.dylib > > -rwxr-xr-x 1 ken.ellinwood admin 1269408 Apr 16 09:23 > > > /Applications/darktable.app/Contents/MacOS/../Resources/lib/libepoxy.0.dylib > > > > I don't see a permissions issue. I think the system is complaining that > > relative paths are not allowed for dylib dependencies. > > > > On Wed, Jul 1, 2020 at 7:26 AM parafin wrote: > > > > > errno=13 is EACCES /* Permission denied */ > > > Maybe you have broken permissions on some files. What does the > > > following command show: > > > ls -l > > > > /Applications/darktable.app/Contents/MacOS/../Resources/lib/libepoxy.0.dylib > > > > > > > > > On Wed, 1 Jul 2020 07:11:08 -1000 > > > Ken Ellinwood wrote: > > > > > > > This is on OSX 10.15.5 > > > > > > > > dyld: Library not loaded: > > > @executable_path/../Resources/lib/libepoxy.0.dylib > > > > Referenced from: > > > > /Applications/darktable.app/Contents/Resources/lib/libgtk-3.0.dylib > > > > Reason: no suitable image found. Did find: > > > > > > > > /Applications/darktable.app/Contents/MacOS/../Resources/lib/libepoxy.0.dylib: > > > > > open() failed with errno=13 > > > > > > > > /Applications/darktable.app/Contents/MacOS/../Resources/lib/libepoxy.0.dylib: > > > > > open() failed with errno=13 > > > > > > > > /Applications/darktable.app/Contents/MacOS/../Resources/lib/libepoxy.0.dylib: > > > > > stat() failed with errno=13 > > > > file system relative paths not allowed in hardened programs > > > > Abort trap: 6 > > > > > > > > Any ideas? > > > > > > > > Ken > > > > > > > > > > > > ___ > > > > > darktable developer mailing list > > > > to unsubscribe send a mail to > > > darktable-dev+unsubscr...@lists.darktable.org > > > > ___ > > > darktable developer mailing list > > > to unsubscribe send a mail to > > > darktable-dev+unsubscr...@lists.darktable.org > > > > > > > > > > > ___ > > darktable developer mailing list > > to unsubscribe send a mail to > darktable-dev+unsubscr...@lists.darktable.org > ___ > darktable developer mailing list > to unsubscribe send a mail to > darktable-dev+unsubscr...@lists.darktable.org > > ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] Rejected images and Lua.
Previously in Lua, the 'rating' field of a rejected image was -1, as stated in the manual. With the development version of Darktable (master revision ae1fe69), a rejected image's 'rating' field is 0, the same as an unrated image. What is the new way of accessing an image's rejected status through the Lua API? -- August Schwerdfeger aug...@schwerdfeger.name ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Parametric Yellow mask
I think that just means your parametric mask's parameters are set such that it is not actually applying to any part of the image -- when the yellow mask view is turned on, the yellow areas show where the mask applies, and the non-yellow desaturated areas where it does not. -- August Schwerdfeger aug...@schwerdfeger.name On Wed, Jan 15, 2020 at 12:59 PM David Vincent-Jones wrote: > darktable 3.1.0+362~g39a47f6aa ... Manjaro/Arch XFCE > > When I try to use the yellow mask with a parametric selection the entire > image turns to monochrome. Is there something that I am missing. > > David > > ___ > darktable developer mailing list to unsubscribe send a mail to > darktable-dev+unsubscr...@lists.darktable.org > ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] Refresh via Lua API.
When I use the Lua function 'darktable.database.move_image' to move an image to another film-roll, the "collect images" module is not updated to show the new film-roll or the change in the image count for the old one. Is there a way to force such an update via the Lua API, without otherwise changing the view? -- August Schwerdfeger aug...@schwerdfeger.name ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Lua Module
The idea of a Lua script that one manually installs in order to avoid the manual Lua-script-installation process does seem a little counterintuitive. But if the script manager is already installed in the '.config/darktable' directory and was working with a previous version of Darktable, there is likely a Lua error someplace -- try running Darktable with the '-d lua' switch and see what comes up in the terminal. -- August Schwerdfeger aug...@schwerdfeger.name On Fri, Jan 10, 2020 at 3:51 PM jys wrote: > On Fri, Jan 10, 2020, at 13:12, David Vincent-Jones wrote: > > > > Yes ... the script manager am I overlooking something? It was > > there in earlier versions but not currently. > > Apologies if I'm pointing out the obvious here, but the script manager is > itself a Lua script, which must be added by the user. It's not part of the > darktable core. > > -- > jys > ___ > darktable developer mailing list > to unsubscribe send a mail to > darktable-dev+unsubscr...@lists.darktable.org > > ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] Exact string matching in collect module.
Was there ever a time when collection by such attributes as title, description, creator, etc., queried for an exact string match not automatically bookended by wildcards -- e.g., if one used collect-by-title with the pattern "Lake", it would only show images with the exact title "Lake", and not, e.g., "Gates of Lakewood Cemetery"? -- August Schwerdfeger aug...@schwerdfeger.name ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-user] Re: AW:[darktable-dev] dt 3.0.0rc0
I have run into this a few times with 2.7 development versions; since at that point encountering a conflict in 'iop-order' numbers caused Darktable to crash, I worked around it by editing sidecar files to eliminate the conflicts, mostly by substituting arbitrary 'iop-order' values. Do you anticipate this causing any issues with the repaired version? -- August Schwerdfeger aug...@schwerdfeger.name On Wed, Nov 13, 2019 at 10:23 AM Pascal Obry wrote: > Dear Axel, > > > is it possible to define "old edits"? > > All images edited with version previous to 3.0.0rc0. > > Starting working on new images is not a problem. > > > Also removing modules... I have hundreds of fotos edited with 2. 7 > > ever since, but not yet exported e.g. for presentation. Would be > > unfortunate, by that time to realize, a bunch of rework is > > necessary. > > Not necessary. And at worst you'll have to reorder some modules. > > We are doing our best to have RC1 very soon which should fix this > issue. > > Best wishes, > > -- > Pascal Obry / Magny Les Hameaux (78) > > The best way to travel is by means of imagination > > http://www.obry.net > > gpg --keyserver keys.gnupg.net --recv-key F949BD3B > > > > darktable user mailing list > to unsubscribe send a mail to > darktable-user+unsubscr...@lists.darktable.org > > ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Full metadata editor
I am in favor of an expanded metadata editor, but I think it should be kept within the module, as this better fits the usual metadata-editing workflow. The unwieldiness might be countered by letting the user specify what set of metadata keys should appear for editing. -- August Schwerdfeger aug...@schwerdfeger.name On Mon, Jul 22, 2019 at 9:40 AM Sam wrote: > Hi, > > I'd like to start working on a more complete metadata editing interface. > I've come up with two possible ways of doing this: > > 1) A pop up window - this gives a lot of space and flexibility to > eventually add as many different metadata-editing features as we could > possibly want. > > 2) Expand the current metadata editor module - I think I could squeeze > quite a lot into there by splitting the fields up into different categories > but it could quite easily become unwieldy and hard to use. > > My preference is for the first option, but it also doesn't really seem > like the darktable way of doing things so I'm interested to hear some other > people's opinions (I'm also open to any other suggestions, or opinions > about if people actually want this feature added). > > Thanks, > Sam > > ___ > darktable developer mailing list to unsubscribe send a mail to > darktable-dev+unsubscr...@lists.darktable.org > ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Crop tool is awkward for my use case
How is this a JPEG vs. RAW issue? I have done a great deal of cropping in Darktable (on both JPEGs and RAWs) and I think that adding the proposed single-drag interaction would speed up cropping a great deal over the current process, no matter the format of the image being edited. -- August Schwerdfeger aug...@schwerdfeger.name On 2/17/19 8:01 PM, David Vincent-Jones wrote: > > Although darktable handles JPG images very well, I think that its > primary market was targeted towards users who shoot RAW with an > expectation of doing more complex processing on individual frames. > Maybe darktable is simply the wrong software for your high production > needs. > > On 2019-02-17 4:08 p.m., Robert Krawitz wrote: >> I find the crop tool to be unwieldly for my common use case, namely >> processing a large number of photographs from shooting sports. >> >> I shoot a lot of basketball and (American) football games for my alma >> mater. My workflow is to import the typically ~2000 photos into >> KPhotoAlbum, review them and select the ones I want (typically 300 or >> so), and create a directory with symlinks to the selected files. >> These are essentially all JPEG; RAW would simply consume too much >> space and slow the camera (Canon 7DmkII) too much. >> >> The postprocessing I do is limited to cropping and rotating, if my >> camera was not level (typically it isn't perfectly level, as I'm >> shooting handheld bursts). I gave up on noise reduction last year; >> the 7DmkII is good enough even at ISO 6400, and additional NR really >> slows things down. >> >> The difficulty is that to crop the frame (always freehand) requires >> the following motions: >> >> 1) Position the mouse near one corner of the image (say, top left), >>which may be nowhere near where I want to crop. >> >> 2) Click and move the top and left edges (via the top left corner) to >>the desired spot. >> >> 3) Move the mouse to the bottom right of the image, which again might >>not be near where I want to crop. >> >> 4) Click and move the bottom and right edges to the desired spot. >> >> With RawTherapee I simply place the mouse at the desired top left >> spot, click and drag it to the bottom right, and I'm done. The extra >> motions with Darktable, especially since they have to start far from >> what may be my point of interest, are awkward and cost maybe 5 seconds >> per image. With 300 images, that's an extra 25 minutes; this past >> Wednesday I shot two games that totaled 700 images, so the extra time >> would have been an hour. >> >> I'd prefer to use Darktable for this purpose, since it's otherwise a >> lot faster. RawTherapee takes maybe 3 seconds or so to export an >> image; Darktable is more like 1 second, not to mention that the rotate >> function is easier in Darktable (right mouse drag). But the current >> behavior of the cropping tool is simply too awkward (I tried it for >> one set and it really did take a lot more time). >> >> I tried looking at the code (in src/iop/clipping.c), but it wasn't >> obvious to me what would need to change to do this. I understand that >> dragging inside the frame is used to move the crop box, but that's >> rarely something I need to do. I have at least two more games this >> season to shoot, and if we make it to the later rounds of the >> tournament, I'm going to have a lot more photos (less selective about >> what I keep). >> >> Perhaps what I really need is a very minimalist program that lets me >> set the crop and rotate and do nothing else, but I haven't found such >> (on Linux). >> >> Thoughts, anyone? > > ___ > darktable developer mailing list to unsubscribe send a mail to > darktable-dev+unsubscr...@lists.darktable.org ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] JPG .. spot removal .. !!
Why should the spot-removal module not be used with JPEG images? I have used it on a great many JPEG images without Darktable crashing (although occasionally the areas do not stay exactly where I put them). -- August Schwerdfeger aug...@schwerdfeger.name On 2/8/19 11:03 PM, David Vincent-Jones wrote: > > I realize after I had done it that spot-removal should not be used on > a JPG file. The result was a nasty dt crash. It might be a good idea > at some point to simply not allow some modules to be used with JPG files. > > David > > > ___ > darktable developer mailing list to unsubscribe send a mail to > darktable-dev+unsubscr...@lists.darktable.org ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Feature request (Cropping module GUI)
The problem with selecting these integers based on commonly-used aspect ratios, is that the only real use for this feature would be in "freehand" mode when cropping to an *unusual* aspect ratio; the common ones like 16:9 are represented in the "aspect" combo box and it is much easier to select the "16:9, HDTV" option to constrain the ratio. -- August Schwerdfeger aug...@schwerdfeger.name On Fri, Nov 16, 2018 at 2:51 PM Jan Ingwer Baer wrote: > On 16-Nov-18 18:26, Heiko Bauke wrote: > > Hi, > > > > Am Freitag, 16. November 2018 schrieb Jan Ingwer Baer: > >> If DT shows the aspect ratio it should try to find the nearest integral > >> fraction (of course with values below 30) like 3:2, 16:9, ... > >> > >> > >> For your exampel it should show 8.2:5, or it should use one of the > >> common denominators x:2, x:3, x:4, x:9 ... > > > > I don't think that this is a good idea, as the user can not know how > close the actual aspect ratio is to the approximate value that is indicated > in the UI. > > > > Heiko > > > Of course DT should not round, but it should show the Ratio with an > integer for the small-side. For me showing 8.2/5 or 3.28/2 (with the > pixel-ratio of the OP) is much more meaningful then 1.62/1. I think it > should be possible to select a usable integer numerator/denominator > based on the fractional ratio. > > If the user wants to create a crop with one of the common aspect ratios > showing it as simple float makes it very challenging to find the right > values. For example : The user wants to create a crop with 16/9. > Displaying the aspect ratio as 1.77/1 is not a big help. > > The challenge is to find the right integer. My idea is to define ratio > ranges for selection : > > 1.2 - 1.4 : set denominator to 3 gives 3.6/3 - 4.2/3 ( ~4/3) > 1.4 - 1.6 : set denominator to 2 gives 2.8/2 - 3.2/2 ( ~3/2) > 1.6 - 1.9 : set denominator to 9 gives 14.4/9 - 17.1/9 (~16/9) > > > ___ > darktable developer mailing list > to unsubscribe send a mail to > darktable-dev+unsubscr...@lists.darktable.org > > ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] Darktable lag on a 4K monitor.
Darktable 2.4.3 and .4, MacOS and Fedora. When using Darktable on a 4K monitor, I am experiencing a UI lag that seems dependent on the size of the application window. For example, when I size the window with dimensions that are half those of the screen, the image highlight in the light table follows my mouse pointer with no noticeable lag. Resizing to three-quarters of the screen dimensions introduces a delay of about half a second between the time the pointer moves and the time the highlight changes. Resizing to full screen increases this lag to about a second. Does anyone know what is causing this? -- August Schwerdfeger aug...@schwerdfeger.name ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Behavior of collect-by-tag changed in Darktable 2.4.0.
After some further examination of the problem, I have opened a pull request to have the change reversed [1] <https://github.com/darktable-org/darktable/pull/1662>. -- August Schwerdfeger aug...@schwerdfeger.name On Mon, Mar 12, 2018 at 11:28 PM, August Schwerdfeger < aug...@schwerdfeger.name> wrote: > Is there any way to replicate the former behavior (collecting by the exact > tag) without doing a two-rule "tag 'Tag' but not tag 'Tag|%'" query? (I am > currently wanting to do some collections of images that have some child tag > but not the parent tag, which is, I think, impossible to replicate with the > two-rule setup.) > > -- > August Schwerdfeger > aug...@schwerdfeger.name > > On Mon, Mar 12, 2018 at 12:21 PM, Tobias Ellinghaus <m...@houz.org> wrote: > >> Am Sonntag, 11. März 2018, 03:48:24 CET schrieb August Schwerdfeger: >> > With Darktable 2.2.5 and earlier, when collecting by tag, if one typed >> in >> > the name of a tag (e.g., 'Parent') it collected only the images with >> that >> > exact tag. >> > >> > With Darktable 2.4.0, this behavior changed so that typing in the name >> of a >> > tag also collects images with any of the tag's descendants in the >> hierarchy >> > (e.g., 'Parent|Child'. >> > >> > Was this intentional? >> >> Most likely, yes. >> >> > -- >> > August Schwerdfeger >> > aug...@schwerdfeger.name >> > >> > >> ___ >> > darktable developer mailing list >> > to unsubscribe send a mail to darktable-dev+unsubscribe@list >> s.darktable.org >> >> > ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] Behavior of collect-by-tag changed in Darktable 2.4.0.
With Darktable 2.2.5 and earlier, when collecting by tag, if one typed in the name of a tag (e.g., 'Parent') it collected only the images with that exact tag. With Darktable 2.4.0, this behavior changed so that typing in the name of a tag also collects images with any of the tag's descendants in the hierarchy (e.g., 'Parent|Child'. Was this intentional? -- August Schwerdfeger aug...@schwerdfeger.name ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Show maximum possible export size in light table?
Here are a few examples of instances where I have had to bypass the collection module, by manual access to the database or otherwise: * It is impossible to search for an exact match to a string. If, for example, I want to search for an image with the exact title "Water", I cannot exclude images titled "Desert with no water". * The tagging module is case-sensitive in its treatment of tags, but the collect module always ignores case. Thus, for example, if I have two tags named "Water" and "WATER", the module cannot be made to distinguish between them. More than once, when I have made a typo and accidentally created a tag such as "WAter", I have had to go into the database to re-tag images. * The current "list of rules" collection structure makes it impossible to formulate some fairly reasonable classes of queries, such as "A but not (B and C)". Also, even if most users do not need more powerful search functionality, one could still make a case for providing it in the API so that the users who do need it could access it through a Lua module without inconveniencing the rest. -- August Schwerdfeger aug...@schwerdfeger.name On Sat, Jan 20, 2018 at 7:19 PM, Mark Feit <mf...@notonthe.net> wrote: > On 1/16/18 3:53 AM, Heiko Bauke wrote: > >> >> Nevertheless, I am not fully convinced that darktable requires such a >> kind of feature. I am pretty sure that such complex search patterns emerge >> from time to time. But for typical use cases the current collection module >> is sufficient. >> > Typical use cases are limited by what the current collection module can > do. The only ways to find out if users are doing things outside of > darktable that could be done inside are to ask or be asked. In my own > case, the only thing I use the collection module for is pulling up whole > folders I've used before. Anything beyond that and I use home-brewed stuff > to paw through my library and then go back to DT and work by folder. > > Not that I think darktable needs to shoot for full feature parity with > Lightroom, but text search is pretty useful and has been available in that > product for almost a decade. > > ... darktable developers should evaluate xapian (https://xapian.org/). >> > Xapian wouldn't be a bad choice, either. I suggested Lucene because it's > very good at what it does, I have a lot of very positive experience with it > and it's in wide enough use that finding developers who understand it isn't > difficult. Most indexing APIs I've put together are a half-dozen calls or > less, so it really wouldn't matter what's backing it up if it's got the > right feature set. > > At any rate, my offer's on the table, it still stands for any indexer and > my feelings won't be hurt if it's ignored. > > --Mark > > > > ___ > darktable developer mailing list > to unsubscribe send a mail to darktable-dev+unsubscribe@list > s.darktable.org > > ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Show maximum possible export size in light table?
I am often having to sift through large batches of already-processed photos to select some number (for entry into photo shows, etc.). There is usually a minimum size requirement involved, and I frequently find myself having to go back into the crop module to see whether or not some cropped photo meets the size requirements. It would be very convenient if I could do this at a glance in the light table instead. -- August Schwerdfeger aug...@schwerdfeger.name On Thu, Jan 11, 2018 at 10:53 AM, Heiko Bauke <heiko.ba...@mail.de> wrote: > Hi, > > > Am 11.01.2018 um 17:46 schrieb August Schwerdfeger: > >> If I did that, I still could not determine the size until *after* the >> export, by examining the exported image. What I am asking about is a way to >> determine the size within Darktable itself, without having to do an export. >> > > this is correct. It remains unclear, however, why this might be an > interesting information *before* export. (Except at the moment when the > crop size is set in the crop module of course.) Just curiosity? > > > > Heiko > > -- > -- Number Crunch Blog @ https://www.numbercrunch.de > -- Cluster Computing @ http://www.clustercomputing.de > -- Professional @ https://www.mpi-hd.mpg.de/personalhomes/bauke > -- Social Networking @ https://www.researchgate.net/profile/Heiko_Bauke > > ___ > darktable developer mailing list > to unsubscribe send a mail to darktable-dev+unsubscribe@list > s.darktable.org > > ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Show maximum possible export size in light table?
If I did that, I still could not determine the size until *after* the export, by examining the exported image. What I am asking about is a way to determine the size within Darktable itself, without having to do an export. -- August Schwerdfeger aug...@schwerdfeger.name On Thu, Jan 11, 2018 at 10:23 AM, Heiko Bauke <heiko.ba...@mail.de> wrote: > Hi, > > Am 11.01.2018 um 17:10 schrieb August Schwerdfeger: > >> For me, the use case is determining, in a speedy and convenient manner, >> the maximum size at which I can print a cropped photo. >> > > if you want to export at maximal size without upscaling set max size to > zero, or set these dimensions to very large values (larger than any > reasonable image dimension) and set allow upscaling to "no". > > > Heiko > > > -- > -- Number Crunch Blog @ https://www.numbercrunch.de > -- Cluster Computing @ http://www.clustercomputing.de > -- Professional @ https://www.mpi-hd.mpg.de/personalhomes/bauke > -- Social Networking @ https://www.researchgate.net/profile/Heiko_Bauke > > > ___ > darktable developer mailing list > to unsubscribe send a mail to darktable-dev+unsubscribe@list > s.darktable.org > > ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Show maximum possible export size in light table?
For me, the use case is determining, in a speedy and convenient manner, the maximum size at which I can print a cropped photo. -- August Schwerdfeger aug...@schwerdfeger.name On Thu, Jan 11, 2018 at 4:43 AM, Roman Lebedev <lebedev...@gmail.com> wrote: > On Thu, Jan 11, 2018 at 7:17 AM, August Schwerdfeger > <aug...@schwerdfeger.name> wrote: > > There is currently no easy way to determine the dimensions of an image > after > > processing occurs (i.e., the maximum size at which an image can be > exported > > without upscaling). I either have to do the actual export at maximum > size, > > or go into darkroom mode, open up the crop module, and try to hold the > > pointer as steady as I can while reading the dimensions off of the > center of > > the crop box. > > > > Would it be feasible to have a light table module showing an image's > maximum > > possible export size? > What for, what's the use-case? > > > -- > > August Schwerdfeger > > aug...@schwerdfeger.name > Roman. > > > > ___ > > darktable developer mailing list to unsubscribe send a mail to > > darktable-dev+unsubscr...@lists.darktable.org > ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] Show maximum possible export size in light table?
There is currently no easy way to determine the dimensions of an image after processing occurs (i.e., the maximum size at which an image can be exported without upscaling). I either have to do the actual export at maximum size, or go into darkroom mode, open up the crop module, and try to hold the pointer as steady as I can while reading the dimensions off of the center of the crop box. Would it be feasible to have a light table module showing an image's maximum possible export size? -- August Schwerdfeger aug...@schwerdfeger.name ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Library size, just for conversation
I have also experienced very little trouble with Darktable reliability- or scalability-wise. One of my databases has ~170k images and has been going without interruption since I first created it with Darktable 1.4.2. The only slowdowns I have noticed are those related to the tagging module, previously mentioned on this list. -- August Schwerdfeger aug...@schwerdfeger.name On Mon, Sep 25, 2017 at 5:02 PM, Patrick Shanahan <p...@opensuse.org> wrote: > * Tobias Ellinghaus <m...@houz.org> [09-25-17 17:44]: > > Am Montag, 25. September 2017, 15:32:55 CEST schrieb Patrick Shanahan: > > > * johannes hanika <hana...@gmail.com> [09-25-17 14:21]: > > > > .. and that is images, not bytes in the db, right? most impressive :) > > > > > > yes, images 16mb,24mb and a very few 12mb > > > > > > > any particular operations that show significant slowdown due to this? > > > > or does it just work? > > > > > > I notice no slow-down anywhere except it takes about 30 seconds on > startup > > > to display. but I usually leave it open as I use it constantly. I > shoot > > > a lot of soccer games but delete all that I do not show. > > > > When disabling the crawler in the preferences (so dt doesn't look for > changed > > sidecar files), does that speed startup up? > > I have the crawler disabled as after working a set, I store them on an nfs > mounted drive. the crawler would be *very* slow. > > on the occasions where I work a set when traveling and use my laptop, I > import them with accompanying xml files to my workstation. I cannot think > of a situation for me where the crawler would be any advantage. if it > happens I need the crawler, I can enable it for that session. > > anyway startup only amounts to ~15 seconds on my workstation and isn't a > bother, just noticable. and startup is only slow when I don't have a set > active, ie: it is accessing the entire collection of 88k instead of > several hundred. > > 12 core i7 > 36 gb > nv GT450 > sata 6 > > tks, > -- > (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri > http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri > Registered Linux User #207535@ http://linuxcounter.net > Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode > > ___ > darktable developer mailing list > to unsubscribe send a mail to darktable-dev+unsubscribe@ > lists.darktable.org > > ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] New packages needed for Darktable build on Fedora.
Recently I had occasion to compile Darktable on a vanilla installation of Fedora 25. After installing all the packages listed on the installation page <http://www.darktable.org/install/#fedora>, I also needed to install gtk3-devel and pugixml-devel before Darktable would compile. -- August Schwerdfeger aug...@schwerdfeger.name ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Tagging module: What the...
I compiled the new version (revision 79e8763) and tried it out on the test images and also on a copy of my main database. The speed improvement is considerable; none of the tagging operations I tried took more than seven seconds to complete. I am looking forward to using this in a stable release. I have experienced the same kind of delays with tags in the collect module, but, oddly enough, not with this version -- neither selecting the "tag" option, nor selecting a tag to collect by, nor applying a color label to an image in a tag-based collection, took more than two seconds with any database I tried. -- August Schwerdfeger aug...@schwerdfeger.name On Thu, Aug 3, 2017 at 4:49 AM, Tobias Ellinghaus <m...@houz.org> wrote: > Am Donnerstag, 3. August 2017, 09:58:01 CEST schrieb Tobias Ellinghaus: > > Am Dienstag, 1. August 2017, 23:45:54 CEST schrieb August Schwerdfeger: > > > I managed to reproduce the problem on a smaller scale using a generated > > > set > > > of 5,000 1x1 PNG images, each annotated with a certain number of tags, > > > with > > > a total of 6,111 across the set. (I will send you these images in a > > > separate message.) > > > > Thanks for that, I was able to reproduce some glacial speeds with that. > > This should be fixed now in master. Some parts are still really slow with > that > many tags though. For example selecting "tag" in the collect module takes > minutes just to show up for me. > > > > When I imported the first 250 of these images into a fresh database in > > > Darktable 2.2.4, attaching one new tag to the lot took about two > seconds. > > > When I imported all 5,000 into another fresh database, attaching the > same > > > tag to the same 250 images took about 10 seconds. > > > > > > I also carried out this same test in Darktable 2.0.7. Importing the > 5,000 > > > images gave me a database file of about 500 megabytes (as opposed to > four > > > with Darktable 2.2.4), and the same tag-attachment operation took four > and > > > a half minutes. When, however, I repeated the operation with the name > of a > > > nonexistent tag in the tagging module text box, it took 10 seconds as > in > > > Darktable 2.2.4. > > > > What I tried was attaching one new tag to the whole lot. It wasn't fun. I > > will investigate, but from a first peek it seems that we are spending a > lot > > of time in sqlite3. So maybe some SQL queries need to be revised, stuff > > might have to go into a transaction or not be done at all. I will see. > > > > > In light of this result, I should mention that the databases I am > having > > > this trouble with were all originally created by Darktable 1.4.2 and > are > > > over 75 megabytes in size. > > > > As it's also slow with a fresh new database we can probably ignore that > > part. > > > -- > > > August Schwerdfeger > > > aug...@schwerdfeger.name > > > > Tobias > > > > [...] > > ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Tagging module: What the...
I managed to reproduce the problem on a smaller scale using a generated set of 5,000 1x1 PNG images, each annotated with a certain number of tags, with a total of 6,111 across the set. (I will send you these images in a separate message.) When I imported the first 250 of these images into a fresh database in Darktable 2.2.4, attaching one new tag to the lot took about two seconds. When I imported all 5,000 into another fresh database, attaching the same tag to the same 250 images took about 10 seconds. I also carried out this same test in Darktable 2.0.7. Importing the 5,000 images gave me a database file of about 500 megabytes (as opposed to four with Darktable 2.2.4), and the same tag-attachment operation took four and a half minutes. When, however, I repeated the operation with the name of a nonexistent tag in the tagging module text box, it took 10 seconds as in Darktable 2.2.4. In light of this result, I should mention that the databases I am having this trouble with were all originally created by Darktable 1.4.2 and are over 75 megabytes in size. -- August Schwerdfeger aug...@schwerdfeger.name On Tue, Aug 1, 2017 at 10:09 AM, August Schwerdfeger < aug...@schwerdfeger.name> wrote: > For privacy reasons, I cannot send the full list of tags from my main > database, but I will try to get together a set that reproduces the problem. > I am also prepared for any needed custom compilations of Darktable. > > I have used a range of GTK versions since I started noticing this issue, > but currently I am using GTK 3.22 on Fedora and whatever version is bundled > with Darktable 2.0.7 for OS X. > > I think that import with tag application has been slowing down as well. > Lately when I import images Darktable just seizes up and only becomes > responsive again some time later, when the import is complete. > > -- > August Schwerdfeger > aug...@schwerdfeger.name > > > On Tue, Aug 1, 2017 at 4:02 AM, Tobias Ellinghaus <m...@houz.org> wrote: > >> Am Montag, 31. Juli 2017, 11:25:02 CEST schrieb August Schwerdfeger: >> > I have used nothing but the Ctrl+T method for some time (I experience >> lags >> > of about 10 seconds between typing a tag name into the module and its >> > actual appearance in the text box). >> > >> > For a while, I could get the Ctrl+T tagging to go faster by keeping the >> > name of a non-existent tag (e.g., "abcdefg") in the module text box, but >> > now even that does not work very well. >> >> That all sounds strange. I just tried with >2k tags in the library and >> everything worked smoothly. >> Could you export the tag list in lighttable and send it to me? I don't >> think >> that the format of the tags makes any difference, but you never know. >> Also, what version of GTK do you use? >> As a last thing you could try: how quick is it when you import an image >> and >> set a tag to be applied during import (in the bottom of the import >> dialog)? Is >> that quick? The reason I ask is that I want to know if it's dt's tagging >> that >> is slow or if it's the GTK side (selecting from a list, auto completion/ >> suggestions, ...). The import module uses our code directly while the >> lighttable parts also depend on GTK. >> >> If all of that doesn't resolve the issue I fear that you have to compile >> darktable yourself so that we can add soem debug prints for you to time >> things. >> >> > -- >> > August Schwerdfeger >> > aug...@schwerdfeger.name >> >> Tobias >> >> [...] > > > ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Tagging module: What the...
For privacy reasons, I cannot send the full list of tags from my main database, but I will try to get together a set that reproduces the problem. I am also prepared for any needed custom compilations of Darktable. I have used a range of GTK versions since I started noticing this issue, but currently I am using GTK 3.22 on Fedora and whatever version is bundled with Darktable 2.0.7 for OS X. I think that import with tag application has been slowing down as well. Lately when I import images Darktable just seizes up and only becomes responsive again some time later, when the import is complete. -- August Schwerdfeger aug...@schwerdfeger.name On Tue, Aug 1, 2017 at 4:02 AM, Tobias Ellinghaus <m...@houz.org> wrote: > Am Montag, 31. Juli 2017, 11:25:02 CEST schrieb August Schwerdfeger: > > I have used nothing but the Ctrl+T method for some time (I experience > lags > > of about 10 seconds between typing a tag name into the module and its > > actual appearance in the text box). > > > > For a while, I could get the Ctrl+T tagging to go faster by keeping the > > name of a non-existent tag (e.g., "abcdefg") in the module text box, but > > now even that does not work very well. > > That all sounds strange. I just tried with >2k tags in the library and > everything worked smoothly. > Could you export the tag list in lighttable and send it to me? I don't > think > that the format of the tags makes any difference, but you never know. > Also, what version of GTK do you use? > As a last thing you could try: how quick is it when you import an image and > set a tag to be applied during import (in the bottom of the import > dialog)? Is > that quick? The reason I ask is that I want to know if it's dt's tagging > that > is slow or if it's the GTK side (selecting from a list, auto completion/ > suggestions, ...). The import module uses our code directly while the > lighttable parts also depend on GTK. > > If all of that doesn't resolve the issue I fear that you have to compile > darktable yourself so that we can add soem debug prints for you to time > things. > > > -- > > August Schwerdfeger > > aug...@schwerdfeger.name > > Tobias > > [...] ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Tagging module: What the...
I have used nothing but the Ctrl+T method for some time (I experience lags of about 10 seconds between typing a tag name into the module and its actual appearance in the text box). For a while, I could get the Ctrl+T tagging to go faster by keeping the name of a non-existent tag (e.g., "abcdefg") in the module text box, but now even that does not work very well. -- August Schwerdfeger aug...@schwerdfeger.name On Mon, Jul 31, 2017 at 3:39 AM, Tobias Ellinghaus <m...@houz.org> wrote: > Am Samstag, 29. Juli 2017, 22:14:09 CEST schrieb August Schwerdfeger: > > Darktable 1.4.2, 1.6.9, 2.0.7, and 2.2.4, on Fedora, CentOS, and OS X. > > > > There is something seriously wrong with Darktable's tagging module. > > > > As I have used successive versions of Darktable with databases containing > > an increasing number of tags, the tagging module has gradually become so > > slow in its operation as to be essentially unusable. > > > > For example, recently, on a database containing ~2500 tags, I attempted > to > > attach a single tag to ~250 images. This operation took approximately > three > > minutes, during which time Darktable was unresponsive and consistently > used > > about 100% of two cores. > > That sounds bad. How did you tag the images? By selecting the tag in the > tagging module and clicking the "attach" button, or using the quick tag > feature (ctrl-t, type, enter)? Could you please try the latter if you > didn't > do so before and tell me if that's faster? > > > By way of comparison, I accessed a copy of the database file directly and > > used an INSERT INTO command to apply the same tag to the same images. > This > > took about 20ms. > > > > Since actually attaching the tag is clearly not taking six minutes of > > processor time, what else is the tagging module doing that could possibly > > be causing these delays (and, what is more to the point, how do I work > > around it so I can actually use the thing again)? > > > > -- > > August Schwerdfeger > > aug...@schwerdfeger.name > > Tobias ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] Tagging module: What the...
Darktable 1.4.2, 1.6.9, 2.0.7, and 2.2.4, on Fedora, CentOS, and OS X. There is something seriously wrong with Darktable's tagging module. As I have used successive versions of Darktable with databases containing an increasing number of tags, the tagging module has gradually become so slow in its operation as to be essentially unusable. For example, recently, on a database containing ~2500 tags, I attempted to attach a single tag to ~250 images. This operation took approximately three minutes, during which time Darktable was unresponsive and consistently used about 100% of two cores. By way of comparison, I accessed a copy of the database file directly and used an INSERT INTO command to apply the same tag to the same images. This took about 20ms. Since actually attaching the tag is clearly not taking six minutes of processor time, what else is the tagging module doing that could possibly be causing these delays (and, what is more to the point, how do I work around it so I can actually use the thing again)? -- August Schwerdfeger aug...@schwerdfeger.name ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Need you help with my darktable lua script
Try moving the declaration of 'combobox' below those of the 'check_button'
widgets.
--
August Schwerdfeger
aug...@schwerdfeger.name
On Feb 25, 2017 5:11 AM, "Holger Klemm" <darkta...@multimedia4linux.de>
wrote:
> Hello,
> I need your help to correct my lua script.
> I have a darktable lua script with which I want to control via a combobox
> the
> check button.
>
> The demo script below works but generates the following error:
> demo.lua:34: attempt to index global 'check_button1' (a nil value)
> stack traceback:
> [C]: in function '__newindex'
>
>
> I have tried everything, but no script without error message.
>
> What am I doing wrong?
> Can someone give me an example how to control the check button via the
> combo
> box without error message?
>
> Many Thanks
> Holger
>
>
>
>
> local dt = require "darktable"
>
> dt.configuration.check_version(...,{4,0,0})
>
> local combobox = dt.new_widget("combobox")
> {
> label = "Combobox",
> value = 1, "Button 1 is checked", "Button 1 and 2 is checked",
> "Nothing
> is checked",
>
> changed_callback = function(selection)
> if (selection.value == "Button 1 is checked") then
> check_button1.value = true
> check_button2.value = false
> elseif (selection.value == "Button 1 and 2 is checked") then
> check_button1.value = true
> check_button2.value = true
> elseif (selection.value == "Nothing is checked") then
> check_button1.value = false
> check_button2.value = false
> end
> end
> }
>
>
> check_button1 = dt.new_widget("check_button")
> {
> label = "Button 1",
> value = true
> }
>
> check_button2 = dt.new_widget("check_button")
> {
> label = "Button 2",
> value = false
> }
>
>
> dt.register_lib(
> "demo", -- Module name
> "demo", -- name
> true,-- expandable
> false, -- resetable
> {[dt.gui.views.lighttable] = {"DT_UI_CONTAINER_PANEL_RIGHT_CENTER",
> 100}},
> -- containers
> dt.new_widget("box") -- widget
> {
> orientation = "vertical",
> combobox,
> check_button1,
> check_button2,
> },
> nil,
> nil
> )
>
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscribe@
> lists.darktable.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Image queries in Lua API.
In terms of the interface, this would not require full access to the SQL database -- only a way to take the existing set of collection rules from 'darktable.gui.libs.collect' and use them independently of the GUI, applying them instead to the table of images from 'darktable.database'. Is this something that would be straightforward to implement? -- August Schwerdfeger aug...@schwerdfeger.name On Fri, Feb 17, 2017 at 3:15 AM, Tobias Ellinghaus <m...@houz.org> wrote: > Am Freitag, 17. Februar 2017, 00:06:36 CET schrieb August Schwerdfeger: > > I am trying to reimplement, using Darktable's Lua API, some parts of > > my workflow that I had previously jury-rigged using external Python > > scripts that modify the database directly. > > > > One of these tasks involves checking that there is no image in the > > database with a given title. In my previous implementation, this could > > be done with a simple database query, but it does not seem to be directly > > supported in the Lua API. Is there any way to do this other than to > > iterate over every single image in the database and check its title? > > No, unfortunately not. I guess adding a way to interact with the sql db > directly would be helpful for some cases. But it's not there. > > > -- > > August Schwerdfeger > > aug...@schwerdfeger.name > > Tobias ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
