Same VI

[Norbac]

Somebody knows if all this scripting feature can be applicated to the same vi (where it is running), instead of create a new VI?

Thanks

A. V.

[Sparc]

Somebody knows if all this scripting feature can be applicated to the same vi (where it is running), instead of create a new VI?

Thanks

A. V.

6020[/snapback]

Scripting features that actually modify VIs cannot be used on a running VI nor one reserved to run. New Object, for example will fail if the owner object is, or is in, a running VI.

However, scripting Properties like "Is Indicator" can be used on a running VI.

Sparc

[Yair]

Scripting features that actually modify VIs cannot be used on a running VI nor one reserved to run.

6021[/snapback]

That's not entirely accurate. You can use the VI class method Fake Exec State to trick LV into thinking that the VI is idle (state 2), but you should be aware that many features will either stop your VI, cause it to crash or cause LV itself to crash, because modifying LV code while the VI is running is almost a sure way to do that.

[Michael Aivaliotis]

That's not entirely accurate. You can use the VI class method Fake Exec State to trick LV into thinking that the VI is idle (state 2), but you should be aware that many features will either stop your VI, cause it to crash or cause LV itself to crash, because modifying LV code while the VI is running is almost a sure way to do that.

6026[/snapback]

OOH nice one, I gotta try me some of that!

[AdamRofer]

That's not entirely accurate. You can use the VI class method Fake Exec State to trick LV into thinking that the VI is idle (state 2), but you should be aware that many features will either stop your VI, cause it to crash or cause LV itself to crash, because modifying LV code while the VI is running is almost a sure way to do that.

6026[/snapback]

Too bad you still can't dynamically change the code even when it's "tricked."