Changed Paxton Filename scheme - #7
Merged
Merged
Conversation
Refactor data handling for paxton_hex to use a padded variable.
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
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.
Change Paxton Filename scheme
This update changes the way Paxton dumps are saved, they are currently saved as
Paxton-ID_<PaddedPaxID>_N.txtthe new naming scheme changes this toPaxton-ID_<UID>_<Block5>_N.txtwith added fallback support for older dumps.The new dump contents are as follows
Net2 Dump File:
and for Switch2 Dump File:
This keeps switch2 with 4 lines and removes the paxID which needed to be done also. I have tested the changes and it is working just fine with the older dumps and the new. I had meant to fit this in with the previous PR but I had not been around today much so I did not make it in time.
I changed the workflow momentarily and reverted it back for the PR so its safe for merge and does not affect your current workflow :)