LabVIEW
"Lock constant value"
Hi,
if you absolutely have to have a difficult to edit item, the best way is to make it a control, set off to either one side of the panel where it cannot be seen when the software is running, or set it to invisible.
Another option (again requireing the front panel) is to put down a numeric, and set it's data range Max and Min to the same, and put the increment to 0.0. - that way when you do need to change it, you can by going back in and editing the data range, but it's no longer a simple case of clicking on the item. It's a simple matter to take a 0 / 1 and turn it into a boolean (compare it to a 0 / 1!)
Another, more complicated way, is to use the configuration .vi's to load in the constants from a .ini file.
You could also put a free label with a transp
arent background over the top of the constant. (easiest) Makes it more obvious what the constant is for, and stops the designer having the ability to directly click on it.
Finally (and not recommended) is to use a PI constant, and another constant to represent the boolean (again comparing to get the True/False. The reason I don't recommend this is the block diagram can become confusing - why use a PI constant is bound to be asked by the first person to look at it!
I agree, lock constant value would be a nice feature for a future version of LV though.
Hope that helps
S.
if you absolutely have to have a difficult to edit item, the best way is to make it a control, set off to either one side of the panel where it cannot be seen when the software is running, or set it to invisible.
Another option (again requireing the front panel) is to put down a numeric, and set it's data range Max and Min to the same, and put the increment to 0.0. - that way when you do need to change it, you can by going back in and editing the data range, but it's no longer a simple case of clicking on the item. It's a simple matter to take a 0 / 1 and turn it into a boolean (compare it to a 0 / 1!)
Another, more complicated way, is to use the configuration .vi's to load in the constants from a .ini file.
You could also put a free label with a transp
arent background over the top of the constant. (easiest) Makes it more obvious what the constant is for, and stops the designer having the ability to directly click on it.
Finally (and not recommended) is to use a PI constant, and another constant to represent the boolean (again comparing to get the True/False. The reason I don't recommend this is the block diagram can become confusing - why use a PI constant is bound to be asked by the first person to look at it!
I agree, lock constant value would be a nice feature for a future version of LV though.
Hope that helps
S.
