You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The current implementation of the custom device adds all DSF components present on the developer's machine as dependent files in the system definition even if some of the components are not required for the configuration. This causes errors in System Explorer if that sysdef is moved to a different machine that does not have all of the same components installed.
Describe the solution you'd like
Only required dependencies should be saved in the system definition.
Describe alternatives you've considered
Dependencies can be added at compile time by adding an ActionVIOnCompile. This removes errors if components are different across different machines. While this is a fairly simple change, the downside is now you will get no errors if a required component is not installed. Deciphering the error returned from VeriStand when a component is not installed is not simple.
Additional context
This isn't a huge issue for most users because if they use the .nipkg installer from the GitHub or the VeriStand suite, they will get all supported components, but for custom components, it would be nice to have this feature.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The current implementation of the custom device adds all DSF components present on the developer's machine as dependent files in the system definition even if some of the components are not required for the configuration. This causes errors in System Explorer if that sysdef is moved to a different machine that does not have all of the same components installed.
Describe the solution you'd like
Only required dependencies should be saved in the system definition.
Describe alternatives you've considered
Dependencies can be added at compile time by adding an
ActionVIOnCompile
. This removes errors if components are different across different machines. While this is a fairly simple change, the downside is now you will get no errors if a required component is not installed. Deciphering the error returned from VeriStand when a component is not installed is not simple.Additional context
This isn't a huge issue for most users because if they use the
.nipkg
installer from the GitHub or the VeriStand suite, they will get all supported components, but for custom components, it would be nice to have this feature.The text was updated successfully, but these errors were encountered: