-
Notifications
You must be signed in to change notification settings - Fork 8
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
Fixes #21 data conversion issue #24
Conversation
…fault byte order rather than big-endian, since this matches the OS/CPU on all targets supported by the DSF.
… viewing a buffer. Also fixed a small bug where characters from a larger number would still be shown when the value lowers to a smaller value.
…s. Changed the default configuration cluster value on front panel to include some string offsets for converting engine channels to string channels.
Bleep bloop! LabVIEW Diff Robot here with some diffs served up hot for your pull request. Notice something funny? Help fix me on my GitHub repo. DSF Core.lvlib--Default Buffer Converter Transfer Configuration.lvclass--Initialize From Settings.vi.png |
Many of the changes made here are aligned with changes in PR#22. Because it is G code, the merging of changes is not straightforward. I will schedule a meeting for us to resolve. |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
love the changes. Thanks!
* set reentrancy and inlining consistent with needs for VIs that need to maintain state for each instance in memory; also use reentrancy to improve parallelization * VI analyzer recommended changes * remove unnecessary layer of subVI * add tests for DSF reentrancy that verify functionality of two parallel instances of framework * separate compiled code from source <AZDO>1097900 https://dev.azure.com/ni/DevCentral/_workitems/edit/1097900 * merge PR#22 changes with PR#24 changes and add unit test for new subVI added in PR #24; changed scope of subVI to public for unit test
What does this Pull Request accomplish?
Why should this Pull Request be merged?
Only makes the above fixes. Does not change core functionality.
What testing has been done?
Ran Framework Test VI.