LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Event registration refnum breaks when new event added

Solved!
Go to solution

@GT123 wrote:

Thank you. I there an other way to solve this. I don`t want to to recreate the controls/indicators.

I like programming e.g. with type def...


 

Since the def of the wire changes when you change the registration node LV HAS to change the wire type. THe best you can do (if you insist on using a sub-VI) is to pop-up on the reg wire after the change and create a control, copy it, open your type def, slect the control and hit ctrl-c to replace it. Save aplly changes.

 

The only other options we have (aside from what I recomended above) is to submit a suggestion to get LV to link ot the type-def but that would be unwieldy since WHO would be the master, the type def of the reg node?

 

That is why I avoid the sub-VI and do the registration on the diagram. Besides, it improves the readablity since you don't have to dig into a sub-VI to see what is being registered.

 

Ben

 

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 11 of 13
(476 Views)

@GT123 wrote:

Thank you. I there an other way to solve this. I don`t want to to recreate the controls/indicators.

I like programming e.g. with type def...


 

Since the def of the wire changes when you change the registration node LV HAS to change the wire type. THe best you can do (if you insist on using a sub-VI) is to pop-up on the reg wire after the change and create a control, copy it, open your type def, slect the control and hit ctrl-c to replace it. Save aplly changes (basically what Ton outlined above).

 

The only other options we have (aside from what I recomended above) is to submit a suggestion to get LV to link ot the type-def but that would be unwieldy since WHO would be the master, the type def of the reg node?

 

That is why I avoid the sub-VI and do the registration on the diagram. Besides, it improves the readablity since you don't have to dig into a sub-VI to see what is being registered.

 

Ben

 

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 12 of 13
(475 Views)

Hello Ben,

ok I think I know what you mean.

The "SubVi" in my application is a Functional global variable to transfer the event registration to other SubVi (who need a user event handling).

Because of this I had to use this "SubVi".

 

I hope you can understand my English Smiley Happy

 

Greetings from Germany

 

0 Kudos
Message 13 of 13
(463 Views)