I am on DT 5.1 windows 11 and I use two Lua scripts. One is rename images and the other is external editors. I use external editors so that I can export images to collections. This is a great feature which I personally feel should be the default behaviour for darktable exports, but that is just my opinion.
The problem is if I open an image directly in darkroom view without initializing lighttable view the Lua scripts don’t load. In the past this has caused me problems when I try and export to collections because the external editor Lua script is not loaded and then DT deletes my export preset with collection as the target.
I have now come to realize that I have to before exporting go to lighttable view to load the Lua script. This is not a major problem but it seems undesirable behaviour and I wonder if fixing this is a minor issue or too difficult to justify the effort by the coders. @wpferguson might know the answer to this since I believe he kindly provided these great Lua scripts. Thanks for your efforts Bill. Greatly appreciated.
I have a similar experience with Win 11. I found that I can import a new folder by drag and drop onto the DT shortcut on the desktop. This will open the application and add the folder, but it won’t activate the script manager.
This isn’t a big deal, but it would be nice if there was a way to get those scripts up and running when importing in this manner.
I agree it is not a big deal and that is why I am reluctant to open a feature request. It was more annoying before I understood why my export preset to collection was being deleted.
I got the bright idea to make the lua scripts easier to install, so I created scripts_installer. I added it to the darktable system luarc file so that it would run on startup.
It got merged, and then…
It seems that I should have checked to make sure there was a GUI before trying to create a UI module
So I fix that and we’re getting close to release, then…
And these were fixed by
which added a function to check if darktable was in lighttable view before trying to create the UI for the module.
Once I understood that it wasn’t just a scripts_installer problem, I added it to all the scripts that create a UI.
End of history lesson
The current situation is script_manager starts all the scripts, but it doesn’t do that until it has created it’s UI, so no scripts are running until script_manager is. I’ve created
to revisit my earlier design decisions and see if there is a better way to start scripts.
My thought is that scripts without a UI should run fine, and scripts with a UI and shortcuts should still be able to use the shortcuts without a UI.
Now for the bad news… I’m in the middle of a programming project that’s 3 months behind and due in 3 months so I’m not going to get to look at this until late July.
Thanks Bill for taking the time to respond. It is a very minor problem and doesn’t need your priority to fix. I am aware that I must go to lighttable before I select my export options with collections as the target. Thanks for this great script and the others you have created.
