Do not apply VI Properties "Run Time Behavior" until the vi is running!

[JÞB]

Many of these VI properties are "Run-time" writeable.  They should not be set while the vi is in an "Idle" state 

[JÞB]

It is my contention that NO runtime writable VI Property should be applied to a VI that is in the "Idle" state.   

Let me give you an example:  Set VI Property FP.Behavior = Modal.

Chat amongst yourselves........ 

[drjdpowell]

I think you need to clarify what you mean by "Idle", here.  Modal VIs, for example, are only modal while "running" in the execution system, and thus not "idle" in that sense, but they are modal while not actually executing, and thus "idle" in another sense.  The historic terminology is unfortunately confusing.  I assume you mean that properties like Modal should only act while the VI is actually executing.

[drjdpowell]

I vote no on your idea, as I definitely have VIs that need the current behaviour.  But a better way of handling modal VIs would be nice.

[JÞB]

@dr Powell

No offense intended but, curiosity only!  What f#$@ing runtime window behavior vi property do you have a necessary?

Show One! Example. Please

[drjdpowell]

An example would be a floating information window, one that is shown to the User but only called when necessary to update the information.  The VI is thus mostly "idle", by your definition, yet needs many of those properties active.

[JÞB]

But.... that's the same thing!  The exact same property a different setting.   Still only needs to apply when running. 

Or, did I miss something from the example VI you DID NOT ATTACH?

Bring something heavy-duty Lead, Gold, Tritium.  A vi?

[drjdpowell]

Floating and Modal already only apply while running, so by "running" you must actually mean executing (ie. in the middle of a call). You want these properties to apply only when the VI is actually executing, correct? I think you are motivated by the problem of an open non-executing dialog, which would be solved by this.  My example is a VI that is being shown while not executing.

[JÞB]

---

@JÞB wrote:

Many of these VI properties are "Run-time" writeable.  They should not be set while the vi is in an "Idle" state 

---

You have still failed to attach an example 

[JÞB]

I have provided examples from experience.   You have not.

Does anyone else want to get slapped?

[wiebe@CARYA]

Note that we cannot attach examples on the idea exchange...

I agree with drjdpowell, this has it's use cases.

Often it's assumed a UI VI has to be continuously running (while loop, event structure) but that's not required. You can (easily) make a VI that doesn't do anything and have another UI VI handle it's events. I use this pattern a lot, although the VIs usually live in a subpanel. But the same could be done for floating or modal VI. The dialog is just a facade...