ni/niveristand-aim-milStd1553-custom-device

Importing empty frames creates empty clusters of data that are compiled and passed around the custom device

Closed this issue · 0 comments

Is your feature request related to a problem? Please describe.
Right now, if a major frame, minor frame, or acyclic frame is empty, it is still generated in the configuration data and compiled into the engine. Ideally, these would be skipped of the XML does not have any contained references for the frames, since they function as containers.

Describe the solution you'd like
I think ideally the Import code could be modified to check for the contained references, and if zero are found, skip parsing that item as if it were not there.

Describe alternatives you've considered

  • We could also continue to pass around the empty containers and notify the user that empty containers are in the XML in some way

Additional context
This was identified during PR #54