Hi Kevin, I think the exporter can only create a preset from the widget's that it controls. The exporter can't "see" into enfusePro and since all those widgets are controlled by enfusePro and not the exporter, the exporter can't set a preference to control widgets it doesn't have access to. To do what you want would require a preset system inside of enfusePro.
Bill On Mon, Feb 25, 2019 at 8:12 PM Kevin Ertel <ker...@g.clemson.edu> wrote: > All, > > I have created a number of lua scripts, some simple, and others more > complex. The most complex is a cross-platform implementation of Holger > Klemm's enfusePro. In going through and re-working this some recently I > thought it would be good to create some presets for this storage with > various different settings selected/enabled. However, I was suprised by > dt's behavior here: > 1) I could only create a single preset for that storage type. The in-built > storage types (such as file on disc) allow multiple presets to be created, > each with unique options. When I go to the storage created by my script I > can make a single preset, and from there on on'y have the options to "edit > this preset" or "delete this preset" > > 2) When creating the preset, my modified values were not saved. I tested > this by deselecting numerous options, creating a preset, resetting the > module (which turned all those de-activated options back on), and then > selecting the previously created preset. None of the options were > deactivated. > > Is this expected behavior for Lua generated storage? As it stands this > makes "presets" for lua storage types pretty much pointless. Is there a way > to enable the traditional preset behavior that exists throughout the rest > of dt? > > ___________________________________________________________________________ > 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
