Skip to content

Stack markers by the shared draw order - #24

Merged
wf9a5m75 merged 2 commits into
developfrom
fix/marker-zindex-order
Nov 12, 2026
Merged

wf9a5m75 merged 2 commits into
developfrom
fix/marker-zindex-order

Conversation

@wf9a5m75

Copy link
Copy Markdown
Contributor

Summary

Feed this provider's native marker order from the shared MarkerDrawOrder helper (core PR), so markers stack the same way on every provider:

  1. larger zIndex ?? 0 in front;
  2. equal zIndex → lower on screen in front, re-sorted when the map rotates;
  3. same screen row → left in front. Independent of add order.

Depends on the core fix/marker-zindex-order PR.

Verification

Two overlapping markers with equal zIndex (north/south), plus a zIndex: 1 marker added first vs a null-zIndex marker added last. Rotating 0° → 180° without re-adding brings the north marker to the front; zIndex 1 stays in front at every heading.

Commits

  • Order markers with MarkerDrawOrder
  • Rank markers into HERE's usable drawOrder range

drawOrder is an integer, so it uses MarkerDrawOrder.ofInt: zIndex first,
then south and west. Unspecified markers in the southern hemisphere no
longer outrank an explicit zIndex.
HERE ignores large drawOrder values: on the TB520FU 2849 worked and 4274
fell back to add order, so the old zIndex * 1e6 encoding let an
unspecified marker cover zIndex 1. Markers are now ranked by
MarkerDrawOrder and given 0..2047, re-ranked on add, change and
rotation.
@wf9a5m75
wf9a5m75 merged commit b799adc into develop Nov 12, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant