search

darktable-org / darktable

darktable is an open source photography workflow application and raw developer
https://www.darktable.org
GNU General Public License v3.0
9.7k stars 1.14k forks source link

problem with border of (sub-)locations #17036

Open diefau opened 4 months ago

diefau commented 4 months ago

Describe the bug

I think displaying the border of a (sub-)location is (in some rare cases) not well done (it seems for me only in highest resolution of a map).

Steps to reproduce

The long(est) straight line on the right of the picture is not a border between Berlin Friedrichshain and Berlin Alt-Treptow (or something else). There is no border between any sub-locations at this line. You can see the right border, if you scroll a little bit more right at that section. (Many thanks for the scrolling with the arrow keys!)

I don't know, if it's a darktable problem or a problem of the used library. I don't know any other program, which can show borders of (sub-)locations (to test it).

Screenshot from 2024-06-21 19-17-30

Expected behavior

darktable should (always) show right borders

Logfile | Screenshot | Screencast

No response

Commit

No response

Where did you obtain darktable from?

downloaded from www.darktable.org

darktable version

4.8.0

What OS are you using?

Linux

What is the version of your OS?

Debian sid

Describe your system?

No response

Are you using OpenCL GPU in darktable?

None

If yes, what is the GPU card and driver?

No response

Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip

No response

github-actions[bot] commented 2 months ago

This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.

diefau commented 2 months ago

Is this bug not relevant enough, that anyone take a look at?

github-actions[bot] commented 5 hours ago

This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.