Build option: remove unused poly VI, but DON'T disconnect tydefs

[tnt]

In several of my programs I use the name of a typedef as an identifier.

Since LV 7, there's an option (which is default ON):

"Disconnect type definitions and remove unused polmorphic VI instances"

When building an application (as small as possible), I only want to choose

for the removal of the unused polymorphic VI's

but I DON'T want to disconnect my typedefs.

So why is this one option in stead of two ...

[Ton Plomp]

In several of my programs I use the name of a typedef as an identifier.

Since LV 7, there's an option (which is default ON):

"Disconnect type definitions and remove unused polmorphic VI instances"

When building an application (as small as possible), I only want to choose

for the removal of the unused polymorphic VI's

but I DON'T want to disconnect my typedefs.

So why is this one option in stead of two ...

I was last day with a NI tech-rep and he replied that this option is added for backwards compatibility. I think you'll have to replace the polymorphic VI's by the actual subVI's. One method i can think off is to make a source distribution where you have the option activated and then reconnect the typedef....

Which of the two is the best for you is up to you..

Ton

[Ed Dickens]

Just curious here, but could you use the controls "Caption" or "Label" or as your identifier?

What are trying to accomplish?

Ed