Document using a non-default decimal separator #197
Conversation
This file contains 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
rtzoeller
force-pushed
the
dev/format-codes
branch
from
9f29b09 to
179914a
Compare
|
Is the chm file compiled during build? (not sure). Or should we add it also? |
|
Looking at the last change to the CHM here, it appears that the CHM is not auto-generated. I'll try to implement this at some point. For now, I manually generated the CHM and pushed it to this dev branch. Here's the view from one of the modified pages in VeriStand: |
PaulDanH
approved these changes
Oct 4, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this Pull Request accomplish?
Document using non-default decimal separators, and that LabVIEW format specifiers may be used in general.
Why should this Pull Request be merged?
Confusion in #196.
What testing has been done?
N/A