You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been reluctant to report this because there is already such a stack of open bugs here plus I couldn't pin-point the problem until today. However, the following screenshots might give (you) more insight.
Bug description
The offsets given in the draw block in YAML seem to not be adjusted (correctly) to screen DPI, unlike the sizes of the icons and other sizes.
The following screenshots are each made on Android each with screens set to different DPI.
Depending on the DPI of the device, the outcome is different. In Android, there is a developer setting ("smallest width") in which one can simulate different DPIs on the same device:
smallest width : large (320) - normal (360) - small (400) - smaller (??) - smallest (514)
Further information
There are three elements visible on the screen:
selected-quest-icons is the pin on which a house can be seen
quest-dots is the white dot that should be placed just so that it is obscured by the lower end of the pin
quest-selection is a marker consisting of a blue circle and should be placed so that it surrounds the icon part of the pin
Thanks for the report, these details are super helpful! The error here looks proportional to DPI so it's possible we've just forgotten to multiply by display density somewhere - I'll check it out.
It's true that there's a backlog of bugs, but some are much easier to address than others so there's still good reasons to file issues :)
I have been reluctant to report this because there is already such a stack of open bugs here plus I couldn't pin-point the problem until today. However, the following screenshots might give (you) more insight.
Bug description
The offsets given in the draw block in YAML seem to not be adjusted (correctly) to screen DPI, unlike the sizes of the icons and other sizes.
The following screenshots are each made on Android each with screens set to different DPI.
Depending on the DPI of the device, the outcome is different. In Android, there is a developer setting ("smallest width") in which one can simulate different DPIs on the same device:
smallest width : large (320) - normal (360) - small (400) - smaller (??) - smallest (514)
Further information
There are three elements visible on the screen:
selected-quest-icons
is the pin on which a house can be seenquest-dots
is the white dot that should be placed just so that it is obscured by the lower end of the pinquest-selection
is a marker consisting of a blue circle and should be placed so that it surrounds the icon part of the pinThis is the relevant stylesheet:
and
In case it matters, the styles for these elements are:
The bug was initially reported at streetcomplete/StreetComplete#1810
The text was updated successfully, but these errors were encountered: