I hadn't thought of 'iconifying' an image for this purpose, thanks. I have only used it where enumerators might want to be able to zoom in on detail of a photo that is 'recognisable' on screen at standard resolution...
This is an understandable (data management / conflict) problem, but it does effectively negate the capability of editing submitted forms on a device if entities are involved - I was discussing this issue with a client only yesterday! These are the unintended consequences of enabling 'allow edits' - I got caught out on another project and had to do some nimble shuffling of data to 'rectify' a problem of my own making.
No, we’ve only addressed polygons drawn in Geoshape questions. There is still an issue with applying a similar change to polygons displayed in Select one from map questions (see: https://github.com/getodk/collect/issues/7084).
Sorry, i was unclear, i tested select poly in the new beta and saw it was still missing stroke width. I meant would the same or similar fix also be able to resolve it for select from map, or was it an entirely different issue to solve.
It's something I've mentioned before, but i definitely don't want to hold up the release for it.
Thanks for the clarification. It’s the same issue as the one I linked above (at least in terms of the root cause), so fixing it should also make using stroke width work correctly.
