Irene,
There is indeed something happening in my state machine that might be part of the problem. I test the issue separetly (slider connect to a change detector (the one from OpenG) connected to a case where true do the calling by ref. Everything is in a while loop). The true case execute twice (one when you start holding the slider and one when you release it). In between, the execution is "halted" on the Open VI ref (the first time the case become true). It seem that my problem is that in my app I do not catch the second execution (which contain the last "valid" value for the slide). I will need to investigate further why it is so (it might be because by the time the second firing occurs, I am still doing other stuff and I am missing it).
As a side note, I am not using event structure in this app.
In any case, thanks for the reply.
PJM
Irene He <[EMAIL PROTECTED]> wrote:
Could that be that when you press down the slider
there is an event occurred that cause you to execute
other states in the state machine, so that it never
gets to the "call by ref" case in your state machine
until you release the mouse?
Just guessing...
Irene
> ----- Original Message -----
> From: PJ M
> To: LABVIEW INFO
> Sent: Monday, January 26, 2004 12:15 PM
> Subject: [A] Call by Ref & Open VI Ref Question
>
>
> Hi everyone,
>
> I have a main VI that call a SubVI containing a call
> by reference.
> The call by ref pass some parameters to the target
> VI.
> One of the parameter is from a control on the main
> VI (UI). As long as I dont hold the control (a
> slider), everything is fine. If I do hold the
> control, the call by reference does not execute
> until I release the mouse (to be more specific the
> Open VI reference does not execute). It would not be
> a problem if the call by reference was not in a
> state machine, (and expected to be called several
> time while the user hold the control), the
> consequence is that my VI execute only once with the
> first value from the control which is always never
> the one when the user release the mouse. It might
> very well be a know behavior (but until now it has
> never been an issue for me). Does it happen because
> my SubVI is in the UI thread (because of the call by
> ref ? )? Is there a way to prevent this from
> happenning (or do I have to redesign my VI around
> that behavior ?)?
>
> Thanks
>
> PJM
>
>
>
--------------------------------------------------------------------------------
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free web site building tool.
> Try it!
=====
Irene He
[EMAIL PROTECTED]
www.hytekautomation.com
www.geocities.com/irene_he
Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!
