I am having trouble with InputText and hope someone can help. It seems that it is either taking two inputs to set my variable or I am accessing the previous setting. I am not sure which and I have been staring at this for hours. Here is my code. Thanks.
We do not have your background image, stylesheet, or powershell script (PortCheck.ps1)... all that makes it difficult to fully test.
I can tell you that your input measure is working, it writes the new port value to the [Variables] section.
Beside what eclectic-tech wrote, I'd say that you should have to include the value which you want to set with the !WriteKeyValue bang into quotes (Command2 option of [MeasureInput] measure): [!WriteKeyValue Variables myport "[MeasureInput]"]. This could be needed especially if the value you'd like to set, contains spaces.
Thank you for both of your responses. I figured out the issue. I had to [!UpdateMeasure MeasureCheck] in order to replace the myport variable before issuing the CommandMeasure, otherwise it retains the old value.
jove1661 wrote: ↑November 9th, 2018, 1:43 pm
Thank you for both of your responses. I figured out the issue. I had to [!UpdateMeasure MeasureCheck] in order to replace the myport variable before issuing the CommandMeasure, otherwise it retains the old value.
Yes... If you set UpdateDivider=-1 on measures or meters, you must manually update them to see any change.
The alternative in small skins would be to let them update at the default skin rate; that is not going to dramatically increase the load.