Fire non-user defined event inside another event

[Mark_BFN]

I want to call a normal/non-user defined event after an operation has occured inside a different normal/non-user definded event. Is this possible?

The reason I don't want to use a user defined event is that if this can be done this way it would be much cleaner implemenation. Also, cleaner than using a sub-vi which would require a lot of wiring.

[chrisger]

hi

you can nest event structures. remember to disable the frontpanel locking for the outer event structure. see also the attachment.

best regards
chris

[Mark_BFN]

Thanks for the reply and example, but I don't think it is what I need. let me try to clarify; is it possible to execute an event inside of an event structure programically? ie: emulate a user clicking on a button.

I don't need to wait for events, but want to execute one.

thanks

[chrisger]

ah, now i got you!

you want to RAISE an event. ok, that's different. in case of just a simple control (any type) you can write the desired value to the "val(signaling)" property of the control. this changes the value AND raises the "value changed" event, just like the user pushed the button. then you can catch this event in the next turn of your loop. if you want to raise other events than just a changed value you might try to use the windows "SendInput" API. this emulates an user input via mouse or keyboard. search for "SendInput" in this forum or at www.MSDN.com, i've seen some postings about this theme.

best regards
chris

[Mark_BFN]

perfect. just what I needed. Thanks!

[Steve Parus]

From my experimentation with this, it appears that the fired event
will not actually execute until the event currently being executed
(the one that fires the other event) is completely finished. The
"time" terminal of the second event idicates the time when it was told
to fire, but it does not actually execute then. You cannot say do
steps 1,2,3 in an event, temporarily leave that event to do code in
another event, then come back to the first event and complete steps
4,5. If the second event is fired after step #3, then steps 4 and 5
will finish first before the second event executes. This contrasts
with other languages such as Delphi were you can leave one event
temporarily.

On Mon, 25 Oct 2004 11:46:45 -0500 (CDT), chrisger o.email> wrote:

>simple control (any type) you can write the desired value to the
>"val(signaling)" property of the control. this changes the value AND
>raises the "value changed" event, just like the user pushed the
>button. then you can catch this event in the next turn of your loop.

[Mark_BFN]

Its good to know how that functionality works. Otherwise it takes a lot of trial and error; especially if you are used to the functionality of another environment. Thanks for the heads up.