add support for the units selected in the display#1
Closed
exadeci wants to merge 2 commits into
Closed
Conversation
Author
|
@tschundler Will you update your repository for this year? Do you think we could add this PR to it? |
Owner
Yes, I'll update for this year. I didn't see the notification for this last year. When golden spike data is released, I'll merge with upstream Meshtastic, and after addressing those conflicts will merge this. (probably around August 1st) |
Author
|
Ok great! |
tschundler
added a commit
that referenced
this pull request
Jul 25, 2024
Not exactly the same change; the interim number must be feet for use with golden spike data as-is.
Owner
|
I created a new branch, https://github.com/tschundler/Meshtastic-device/tree/brc-2024 and included a commit to do this. I tested and get a reasonable 432km to the man |
tschundler
pushed a commit
that referenced
this pull request
Jul 7, 2025
Formatting for PR meshtastic#4661
tschundler
added a commit
that referenced
this pull request
Jul 7, 2025
Not exactly the same change; the interim number must be feet for use with golden spike data as-is.
tschundler
added a commit
that referenced
this pull request
Jul 13, 2025
* BRC 2024 Golden Spike Data * Configurable units, based on pull #1 Not exactly the same change; the interim number must be feet for use with golden spike data as-is. * update meshtastic 2.6 with BRC 2025 Golden Spike * add performance improvements * fixed roads + script to make roads * refactored string generation to allow getting hour & street separately for multi-line display * Display BRC location on self location page * formatting fixes via `trunk fmt` * Show BRC location of favorite node --------- Co-authored-by: Gaetan Gueraud <exadeci@gmail.com>
tschundler
added a commit
that referenced
this pull request
Jul 13, 2025
* BRC 2024 Golden Spike Data * Configurable units, based on pull #1 Not exactly the same change; the interim number must be feet for use with golden spike data as-is. * update meshtastic 2.6 with BRC 2025 Golden Spike * add performance improvements * fixed roads + script to make roads * refactored string generation to allow getting hour & street separately for multi-line display * Display BRC location on self location page * formatting fixes via `trunk fmt` * Show BRC location of favorite node --------- Co-authored-by: Gaetan Gueraud <exadeci@gmail.com>
Owner
|
integrated in meshtastic#7252 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I'm glad I've found your project it'll be so useful on playa.
I however use metric units and I figured rather than just changing the variables for me we could make it compatible with the units settings of the display.