The histogram overlay control for exposure and black level It’s too easy to inadvertently mess up exposure when cycling through scopes (especially with a Wacom tablet) and it adds unnecessary GUI motion events and redraws. The easter egg video game Not funny if you happen to be with a client on April 1st and your working app opens on a silly game that can’t even be closed with Ctrl+Q. The problem is GPhoto2 is known to break something different at each new release, so it’s simply not worth the trouble to maintain a GUI over a Schrödinger cat. The tethering view is merely a GUI over Gphoto2, much like Entangle.
Perhaps it works fine in those cases.- What was removed from mainstream darktable Features The tethering view It relies on the lib GPhoto2 which is super brittle and buggy. Probably most people are either using the last OS version, or installing from source and updating as soon as a new version comes out.
#Darktable performance update#
My guess is that it depends what version you updated from, and because I didn’t update my OS for a couple years I was updating from an older version than people normally do. It remembers my other settings, so there isn’t a problem with it writing the config file. Which is itself buggy, so while I wouldn’t rule out that they’re doing something strange, it doesn’t seem like it should really matter to this problem if darktable knows it wants to make the adjustment, it should be able to figure out if it did it already. Sure, if somebody really wants to investigate it, I’m on Fedora Linux 35, and I’m calling it from Shotwell. Such an investigation will take more time than applying a workaround of manually forcing darktable to skip the update, but it also helps more people. Knowing more about the problem (operating system external program that calls darktable possibly the concrete command-line arguments it uses to invoke darktable) would help us all understand and solve the problem, whether it lies with your environment (wrong path, file permissions or whatever), or with darktable (a bug in the config update).
#Darktable performance code#
Maybe it is just a one byte error or something, but most bugs require some function to be rewritten, and so most pull requests get denied, and the original author would rather just fix it themselves so the style of code doesn’t change. Maybe somebody thinks it isn’t needed? If the deprecated module is actually disabled in the future, of course I’d make a fix right away, but for now I can still just use the old one.Ī pull request to fix what might be a simple bug sounds like a simple thing to do, but why is the bug there in the first place? Fixing the bug likely would require cleaning up a whole section of code.
The only thing I’ve noticed so far that needs doing, that isn’t already being done (stepping on toes isn’t viewed as helpful) is to fix the rotate module so you can rotate more than ☒0degrees, but even there, why did the old module get deprecated without a useful replacement? I’d have to try to figure out why that was done, otherwise I might just be wasting my time. In my experience, every open source project with a lot of users has a long line of developers asking, “How can I help?” and being told, “Well, find something that needs doing, if you can!” That’s really the hard part what needs doing? Generally if you ask a core development team if they want volunteers, what they want is people to write better documentation and do testing on additional platforms.
0 kommentar(er)
