Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

The current recording track disappears when scaling on engine 1 #21193

Closed
Nine-Tailed opened this issue Oct 30, 2024 · 4 comments
Closed

The current recording track disappears when scaling on engine 1 #21193

Nine-Tailed opened this issue Oct 30, 2024 · 4 comments
Assignees
@Chumva
Labels
and-bugs
Milestone
5.0-android

Comments

@Nine-Tailed
Copy link
Contributor

Description

If you scale a track so that it doesn't fit entirely on the screen when recording it, it disappears. The problem is only with rendering engine 1.

Screenrecorder-2024-10-30-20-20-07-41.mp4

Steps to reproduce

described above.

Actual result

the track stops displaying

Expected result

the track does not disappear

Your Environment (required)

WARNING Crash-Logs MAY contain information you deem sensitive.
Review this CAREFULLY before posting your issue!

OsmAnd Version:OsmAnd~ 4.9.0#3600m, Дата выпуска: 2024-10-29
Android/iOS version:
Device model:
Crash-Logs: ?
@Nine-Tailed Nine-Tailed changed the title The current recorded track disappears when scaling on engine 1 The current recording track disappears when scaling on engine 1 Oct 31, 2024
@yuriiurshuliak
Copy link

The bug has been confirmed. To reproduce it, switch the rendering to Version 1, start recording your route with Trip Recording enabled, and attempt to zoom in on the recorded path.

The result shows that at certain zoom levels, the recorded track disappears from map.

OsmAnd~ 5.0.0#3623m, released: 2024-11-01

video_2024-11-01_17-40-59.mp4

@Nine-Tailed Nine-Tailed mentioned this issue Nov 7, 2024
Closed
@Nine-Tailed
Copy link
Contributor Author

@vshcherb, please note this bug.

@vshcherb
Copy link
Member

Yes but low priority as it only legacy rendering engine

@vshcherb vshcherb added this to the 5.0-android milestone Nov 28, 2024
@yuriiurshuliak yuriiurshuliak mentioned this issue Dec 21, 2024
Closed
@Chumva Chumva self-assigned this Dec 23, 2024
@yuriiurshuliak yuriiurshuliak mentioned this issue Dec 30, 2024
Open
Chumva added a commit that referenced this issue Dec 30, 2024
@Chumva
Fix #21193
c5f7144
@Chumva Chumva closed this as completed in 0e1372b Dec 30, 2024
Chumva added a commit that referenced this issue Dec 30, 2024
@Chumva
Merge pull request #21648 from osmandapp/fix_#21193
8d3b45a 
Fix #21193
@Zirochkabila
Copy link
Contributor

Testing 1

OsmAnd~ 5.0.0#4062m, Released: 2025-01-06 - Fixed

@sonora sonora mentioned this issue Jan 8, 2025
Open
sapstern pushed a commit to sapstern/OsmAnd that referenced this issue Jan 12, 2025
@Chumva @sapstern
Fix osmandapp#21193
6f5b4e1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Chumva Chumva

Labels
and-bugs
Projects
None yet
Milestone
5.0-android
Development

No branches or pull requests
5 participants
@vshcherb @Nine-Tailed @Chumva @Zirochkabila @yuriiurshuliak