search

ni / niveristand-aim-milStd1553-custom-device

Custom device for AIM MIL-STD-1553 hardware
MIT License
1 stars 2 forks source link

Scripting API for Ballard and AIM create naming conflict when used in the same project #101

Closed fmussi closed 1 year ago

fmussi commented 1 year ago

Describe the bug When working on a project where I need to script custom devices from either Ballard and AIM. If I mix both APIs in the same project, I get several naming conflicts as there are VIs with the same name, for example:

Shared folders (\addons\VeriStand Custom Device Scripting APIs\Ballard MIL-STD-1553\Shared and the one for AIM) have VIs / ctls. with same name Import folders have lvlib with the same name

To Reproduce Use scripting APIs for both Ballard and AIM on the same project to

Additional context One option I quickly tested is the creation of new libraries for those folders that don't have any and renaming the existing libraries with the same name. Something like:

Vendor / Protocol Current namespace Proposed namespace
AIM / 1553 MIL-STD 1553 Import.lvlib AIM MIL-STD 1553 Import.lvlib
Ballard/ 1553 MIL-STD 1553 Import.lvlib Ballrd MIL-STD 1553 Import.lvlib
AIM/ 1553 no namespace AIM MIL-STD 1553 Shared.lvlib
Ballard/ 1553 no namespace Ballard MIL-STD 1553 Shared.lvlib