| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
Second data point needed for the mobile pinch issue: the status line
now shows pointer activity (pointerdown id/pts, pointercancel id/pts,
pinch distance) so it is visible on the phone whether the second
pointer arrives at all or whether the browser cancels pointers when
pinching. Also: only capture the primary pointer (capturing every
finger confuses some mobile browsers), and pointercancel now removes
just that pointer instead of clearing the table — a browser that
'cancels' finger one as finger two lands no longer makes pinch
impossible to form.
|
|
Firefox on Android may consume two-finger pinch for page zooming
despite touch-action: none on the canvas. Disable page zooming via
the viewport meta (maximum-scale=1, user-scalable=no) so the gesture
reaches the app as pointer events; the app provides its own zoom.
Also join touch pointers seen only via pointermove into the pointer
table, so a swallowed second pointerdown cannot break pinch.
|
|
- two-finger pinch on the viewport canvas: pointer table tracks all
active pointers; pinch emits zoom anchored at the finger midpoint
plus pan by the midpoint delta; a second finger cancels an in-flight
pan/marker drag, the remaining finger resumes panning, and pinch
gestures never fire a click
- 100dvh (with 100vh fallback) for the app shell: on mobile browsers
100vh includes the area behind the dynamic URL bar, which pushed
the compass strip below the visible fold
- file input accepts image/* so Android pickers offer all photos and
transcode exotic formats (HEIC) to decodable ones
|
|
- core: track::load_gpx_from_bytes (path wrapper delegates to it;
same hardening: size cap, no entity expansion, direct-child <ele>)
- sidebar: 'Load GPX Track…' button + hidden .gpx file input; the
track swaps in via remove_hills(FLAG_TRACK_POINT) + add_hills, so
marker hill indices never shift (track hills always live at the end
of the hill list)
- rendering: desktop parity — consecutive visible points joined with
round-cap strokes, width = scale*track_width/(dist_m*10) clamped
to [1,1000] image px, red (blue when hidden by terrain); a Track
width slider (50-1000 m, default 200) appears in Display once a
track is loaded
- track points and duplicates are excluded from guide dots, hover and
click hit-testing (they are scenery, not markable peaks)
|
|
The desktop lays out labels in alpha-descending order (the C
pointer-array sort), which on screen means right to left — so the
leftmost peak of a collision cluster ends up on top of the stack.
The web port sorted by screen x ascending, inverting every stack and
making labels look assigned to the wrong peaks. Sort descending; the
break-early scan in layout_label_y stays valid because it only relies
on monotonic x, and labels extend rightward just like in C.
Verified against the desktop rendering of the same panorama photo and
a right-to-left replay of the layout in the label simulator.
|
|
The C++ original draws a cross + vertical + horizontal leader for
every labeled peak, not just marked ones. Without them, collision-
pushed peak labels float unattached and it is impossible to tell
which dot they belong to (verified by replaying layout_label_y on a
synthetic ridge scene). Peak leaders use the muted pale green of the
label text; marker leaders stay yellow with the small cross.
|
|
Display > 'Show peak labels' toggle (off by default): every visible
peak gets its name drawn next to its guide dot, like the desktop
version. Labels join one combined collision-avoidance layout pass with
the marker labels (same layout_label_y), so marker labels keep
priority and nothing overlaps. Unmarked labels are tinted pale green;
hidden peaks and already-marked peaks get no duplicate label.
Candidates now carry name + marked flag (DotView), markers carry the
hill index (MarkerView::hill) for the dedup.
|
|
'gipfel web' is taken by an existing related project. The browser app
is now wipfel — web based gipfel photogrammetry for mountain images:
crate gipfel-web -> wipfel, updated titles, docs, plan and dev script.
The shared engine crate stays gipfel-core.
|