LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

properties not being written in xcontrol

When I write properties to a control on the FP of a facade VI, it has no effect; the property values aren't being written.

Is this a known bug? Or possibly a corrupt control or VI?  Is there a workaround?

The atttached file is a copy of the facade VI's code, unlinked from the rest of the xcontrol.

Here is an image of the offending portion:

Captured001.png

"If you weren't supposed to push it, it wouldn't be a button."
0 Kudos
Message 1 of 7
(3,534 Views)

Your Y-scale is set to Autoscale.

 

Perhaps it is re-autoscaling between writing a value to YMax and reading it back.

0 Kudos
Message 2 of 7
(3,514 Views)

Turning off Autoscale for Y doesn't help.  Also, isn't autoscaling only supposed to happen when a new value is written to the control?

"If you weren't supposed to push it, it wouldn't be a button."
0 Kudos
Message 3 of 7
(3,504 Views)

You're probably right.  Just something I noticed that would seem to make sense.

 

It might be a complication (or even a bug) with Xcontrols.  They are something I've never messed with.

0 Kudos
Message 4 of 7
(3,495 Views)

I found the workaround, and it's very strange.  If I write to properties, then do notthing else, the property values aren't updated.  If I write to them, then read them back, the values read back are bogus, but doing the read, causes the previously written values to be applied.  Thus in the code shown, the readback of the Y-scale max returns 0 but forces the update.

Note: If you have a property node that reads a property, but you don't have the output wired to anything, the read of the property will not happen.

 

 

"If you weren't supposed to push it, it wouldn't be a button."
0 Kudos
Message 5 of 7
(3,488 Views)

Does that mean that the property did get written, but it didn't actually occur until after you tried to read it and got the wrong value?

0 Kudos
Message 6 of 7
(3,479 Views)

That seems to be the case.

"If you weren't supposed to push it, it wouldn't be a button."
0 Kudos
Message 7 of 7
(3,455 Views)