Rename User Event

[nicolasB]

Hello,

I've created a variable manager in a functional global which generates a user event for each changed rsp set variable.

The attached code is an example reduced to the minimum.

It works fine but my question is if any of you see a possibility to get different names for the user events.

Like you can see in the "MyVar1 and 2 Indicator.vi" both user events in the event structure have the same name and this is very inconvinient when the number variables/events increases.

regards,

nicolas

[shoneill]

QUOTE (nicolasB @ Feb 5 2009, 02:14 PM)

Hello,

I've created a variable manager in a functional global which generates a user event for each changed rsp set variable.

The attached code is an example reduced to the minimum.

It works fine but my question is if any of you see a possibility to get different names for the user events.

Like you can see in the "MyVar1 and 2 Indicator.vi" both user events in the event structure have the same name and this is very inconvinient when the number variables/events increases.

regards,

nicolas

The User Event takes the name of whatever control or constant used to type it on creation AFAIK.

I personally would prefer a NAME input for the creation of user events, but that's currently not how it's implemented. The current situation basically prevents creating user events in a loop because they than all have the same name.

Shane.

[Aitor Solar]

Probably the easiest solution is to typecast the user event reference into a user event reference with the name you want.

Saludos,

Aitor

[Mark Smith]

QUOTE (nicolasB @ Feb 5 2009, 06:14 AM)

Hello,

I've created a variable manager in a functional global which generates a user event for each changed rsp set variable.

The attached code is an example reduced to the minimum.

It works fine but my question is if any of you see a possibility to get different names for the user events.

Like you can see in the "MyVar1 and 2 Indicator.vi" both user events in the event structure have the same name and this is very inconvinient when the number variables/events increases.

regards,

nicolas

It appears the event name in the event handler structure is going to be the same as the name of the control that it references. So, the only way I see to do this is to get the event in the called VI and load it into a control with a new name and then use that control to register the event. I don't really like this (it requires loading the control with a local variable or property node since just passing the data thru the control won't affect it) but it does work - see attached VI. Maybe someone else has a better idea.

Mark

http://lavag.org/old_files/post-1322-1233843289.vi'>Download File:post-1322-1233843289.vi

OK, the typecast looks interesting but I think it would require care to make sure you don't get a run-time failure from an improper cast

[LAVA 1.0 Content]

QUOTE (mesmith @ Feb 5 2009, 03:16 PM)

OK, the typecast looks interesting but I think it would require care to make sure you don't get a run-time failure from an improper cast

That is no problem, this is all done in compile time (the name of the event is part of the 'wire').

Ton

[Mark Smith]

QUOTE (Ton @ Feb 5 2009, 07:50 AM)

That is no problem, this is all done in compile time (the name of the event is part of the 'wire').

Ton

I was thinking more if your event datatype changed and you did not update the control/constant wired to the "Type" input you could get some really interesting run-time results!

Mark

[nicolasB]

Thanks at all!

I think the Type Cast solution is working good for me.

regards,

Nicolas