darktable
darktable copied to clipboard
darktable-org
Improve generic range filters
As with the star filters, the generic range filters have some readability issues (arguably more so) when pinned to the top bar. For example, I managed to pin the following filters (capture date, aperture, focal length) to the top bar. This is what it looks like:
The only way to read these filters is by hovering over and waiting for the tooltip to appear (though readability is better in the collection filters module).
I agree that these filters make selecting things easier but they are virtually impossible to read so IMO they still only do half a job. I'm also not convinced that the histogram-like display is particularly useful without some axis labels (which obviously would make the widgets too high/complex). I kind of have similar feelings about the timeline view in the lighttable, but at least that has year indicators along the x axis.
This issue did not get any activity in the past 60 days and will be closed in 365 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
there is a good reason when dealing with dates everyone uses a calendar ... those other two should be drop downs you need to see the actual values, are we to remember some QR patterns instead of it saying 50mm or F1.8 ? this is crazy
Maybe we should highlight and label the the most commonly used value.
This way it would be clear which pattern shows which criteria:
If the drop-down-icon is used to open the list of values, then right-click could be used to change the graphical interface to a text-field entry:
focal length: >=50
Good that you're thinking of stuff, but IMO that's not any better, and potentially misleading if you're only showing a single value.
This issue did not get any activity in the past 60 days and will be closed in 365 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.
This issue did not get any activity in the past 60 days and will be closed in 365 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.
This issue was closed because it has been inactive for 300 days since being marked as stale. Please check if the newest release or nightly build has it fixed. Please, create a new issue if the issue is not fixed.