I don’t use Styles module a lot, but today I looked for it in the lighttable and it wasn’t there. After several tests with the .config/ darktablerc file, i found out that the line plugins/lighttable/1/styles_visible= shows the FALSE state. If I change it to TRUE an run DT, the module doesn’t appear and the line gets to FALSE again.
I don’t know why I thought that this has to do with LUA, so I have disabled LUA scripts and (after changing again the state to TRUE) the module has appeared.
Does anyone know what happens? It seems that one of the scripts changes the state of this module.
Hi Bill!
I have had thought about this, so I have opened the file darktablerc and changed the line plugins/lighttable/1/styles_visible= to TRUE, just in case saw if line lua/script_manager/contrib/autostyle= was FALSE and restarted DT with LUA activated, but Styles module doesn’t appear, as you can see in the image. It should have been below History stack module.
So it seems that it hasn’t to do with autosyle.lua script. What else can be? Is there something more I can do to test?
I will try to disable ALL the scripts I have enabled an see if one of them could be the guilty.
EDIT:
After trying all of the scripts one by one I discovered that the problem is the Autogroup script. If I let it disabled, the Style module doesn’t disappear. Now it would be interesting to know why.
AutoGrouper.lua. I knew it was one of the auto… scripts, but I guess I should check instead of relying on memory.
I started researching to see why the styles module is turned off. It appears that I introduced that change as part of the API 7.0.0 updates. I have no earthly idea of why I hid the styles module nor can I think of any good reason to do that, so I’ll fix it.
