-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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.
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
Cannot set night mode for Custom Route Line Colour #21870
Comments
The bug has been reproduced following these steps:
Actual Result: Expected Result: OsmAnd~ 5.0.0#4329m, released: 2025-02-07 video_2025-02-07_16-31-57.mp4 |
Thanks @yuriiurshuliak for reproducing the bug, is there a workaround that I can use to switch to dark theme during navigation? Or, I have to wait until this bug is fixed in future releases of osmand+? Again, thanks for your support. |
@alahmed Have you tried these methods to enable Dark mode? Check if they work, and if not, let us know:
|
Thanks @yuriiurshuliak for your response, I need to enable dark mode while navigating. And the steps you've given me don't enable dark mode during navigation. I would assume that "Customise Route Line" is the only option. I was thinking if we cannot change it using the GUI, can we change the default.render.xml config file to achieve the same result? This config file is hugs (around 12,000 lines of code) and I don't want to mess with the file without knowing what I'm doing in the first place. |
Description
When selecting Night mode under Settings -> Customise Route Line -> Custom, the change does not apply and the setting automatically reverts to Day mode!
Steps to reproduce
Go to Settings -> Customise Route Line
Change Colour from the drop-down list from Map Style to Custom
Change the theme from Day to Night mode
Click Apply
Actual result
Day mode under Custom colour instead of Night mode
Expected result
Night Mode after applying the change for Custom colour
Your Environment (required)
WARNING Crash-Logs MAY contain information you deem sensitive.
Review this CAREFULLY before posting your issue!
The text was updated successfully, but these errors were encountered: