DQMH Consortium Toolkits Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

Conflict with "Modules" virtual folder

I'm not sure if this is a bug, maybe just a "gotcha". I tried to add a DQMH module to my project named "Camera.lvlib" (first one of the project). I already had some instrument drivers in the project, one of which has a virtual folder named "Modules". Instead of making a top-level virtual folder named "Modules", my new DQMH module went into the existing one under my instrument driver.

 

There was an error that resulted. I made the top-level "Modules" folder and put my new "Camera.lvlib" module there.

 

capture.png

0 Kudos
Message 1 of 2
(609 Views)

I agree this is a bug, the scripting tools shouldn't try to put the new files inside nested 'Modules' or 'Testers' folders. I've filed Issue #850 to the DQMH Consortium to fix this problem in a future DQMH release. Thanks for reporting it.

Message 2 of 2
(589 Views)