-
Notifications
You must be signed in to change notification settings - Fork 49
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
Show Profile Number on display #670
Comments
Thanks for asking! This is a reasonable request.
This is a good idea but requires custom fonts which we're not able to do at this time. The number of characters is pretty limited to 6 (usually). Do you think '3_MyPr' is recognizable for 'MyProfile' in profile #3? |
That sounds like a good way to do it, since my profiles are for different city locations, ie: Fullerton is profiles #4 that would show as '4_Full'. |
This has been fixed in v3.10. |
That is great, I see there is an extra space before the number 5 profile. |
What is your #5 profile name? The text is centered so you may see '5_ABC' centered (spaced before/after) for shorter profile names.
Please create a new request.
Flattery will get you everywhere, including feature requests. Thank you for saying thank you! |
I checked my profiles and the issue is with 5_emlid, would this cause the extra space to show in front of the number? I will put in a new feature request, and again keep up the good work. |
Subject of the issue
A number to indicate which profile is being used on the Facet RTK screen.
Your workbench
v3.8, v1.32
Bluetooth, WiFi, SW Maps transmitting NTRIP back to the device
Steps to reproduce
The number for the profile could be placed where the recount number is for debugging, maybe a dash under the number to indicate it is a profile and not the reset number? It could flash between the profile number and the debug number when debugging?
Expected behavior
When the unit starts the number displayed would be the profile in use.
Actual behavior
The unit starts and there isn't any indication of the profile in use at the moment.
The text was updated successfully, but these errors were encountered: