Then I tried replacing my dev version by copying the darktable folder to my J drive and changing the bat file used to start the dev version. I started it the new version, and it looks like this:
Both installations are set to run elegant-grey. I’ve looked at preferences and don’t see a setting to account for the different look. Moreover, in the second installation, clicking on an image doesn’t select/highlight it. When I double-clicked on one, it opened in darkroom, but upon returning to lighttable, it looks like this:
You have to look for your personal config files, not for the files of the installation. In linux you find them in ~/.config/darktable in windows I don’t know.
On darktable 3.2 and dev versions, check before preferences dialog window and see which theme is used and if modify theme with css tweaks below is checked (if yes, start by unchecking it).
On what you made, you have an issue with a CSS personal tweak and especially a path issue. darktable don’t find the correct CSS on your dev version, that’s why you have that awful GUI.
When I read directions for installing the dev version, the post said rename darktable.exe to make sure there was no confusion, and of course, use that name in your bat file. I did the same thing with 3.2.1. Bad idea! Once I changed the name back and the bat file to darktable.exe, dt ran just fine.
I think I’ve built the right version, it says it’s 3.2.1, e.g. there’s a search in shortcuts, e.g. there’s a “user modified” preset in white balance. However there’s still a checkbox for basecurve presets in settings - I read this has been removed.
There’s a checkbox to ‘auto-apply per-camera base curve presets’ which should only be used in combination with the ‘display-referred’ pixel workflow defaults. It’s the latter option that replaces the ‘auto-apply base curve’ preference.
Not much, 3.2 had many new features already. 3.4 will mostly concentrate on fixing some bugs uncovered after the huge 3.2 work. 3.4 will also have many speed improvements.
I also hope for an update of the user manual. Work has already been done on this part but there is some more work to be done.
Great news! Are there any plans to add some documentation for the Tone Equalizer module? I have zero clue what sort of mask I need for a given task, nor how to achieve it.
I noticed this but its a bit distracting I might actually turn it off…I took a quick look and the info seemed cryptic…I guess I should pay more attention…likely the host of small numbers and my eye sight…
Yes, there is lot of work on the documentation at the moment. My plan is really to have a full documentation for 3.4 and we are very close from this target already