Why do Single-Process shared variables create a single variable VI in my dir.

[davidreed10]

I'm creating an application VI following the example which is created by starting a two loop Real-Time project which creates a Single-Process shared variable and a Network-Published shared variable for each variable that needs to be sent to a non-Realtime host VI. Each of the Single-Process variables shows up as a VI file with the following format: <variable library>_<variable name>.vi. The VI has one control which is the shared variable. I have a large number of variables and this creates a lot of clutter in the directory. I expected them to be rolled up into the library file. Is this expected behavior? I'm attaching a screen shot to show the behavior.

[Stephen_S.]

Hi davidreed10,

This is a known issue with single process variables that are saved in a project that has the .lvproj and .lvlib files initially saved in different locations, as is the case with Real-Time projects. This has been previously reported to our R&D department with the ID #56580, and is being worked on for a fix in a future release of LabVIEW.

This should be only a problem for Single-Process variables, and not Network-Published variables, so if you want to keep your folder from getting cluttered up, changing the variable types to Network-Published should get you around the problem for now.

Regards,
Stephen S.