Quote: Originally Posted by
jeffkay 
I oversimplified the last example--it was clear that you could do that all in one block. Let's say you have two separate tasks like setting a clock running and then using that variable later in an input statement?
To set the variable, you would create a Then-Do after the first logic block that would change the variable to whatever value. Either "#" or "d#". "d#" is to change it by some amount. So to change it by +2, then it would be "d2". To change by -42 it would be "d-42". Alternatively you can use the "set" feature of variables which will set the variable to the value of whatever is before it. This is done in the actual logic layout.
To then use the value of the variable you place the variable with the "get" feature, and that will insert the current value of the variable into whereever that is.
Quote: Originally Posted by
jeffkay 
Anyway, what about those Root logics and how do these labels get created or edited?
Labels as in just the name? If so it is in the properties area of each logic block. It serves no purpose other than to help you organize things.
Quote: Originally Posted by
jeffkay 
My next question is about latching or not latching. In my test, I made an input close a relay after getting above a threshold. Since there was a GUI button onscreen, I noted that the button latched and my relay would not reopen until the GHI button was toggled. So what do I do if I wand to undo the latch made by the Ninja Kitty?
Jeff
When a button is pressed, it constantly sends out it's vote. If you want to override the button with a logic function you could set logic's vote priority to something higher than the buttons. So if the button is low priority, set the logic to medium priority. Or you can have the button change a variable. Then a logic block check the variable and if it equals some value turn on. Then you can manipulate the variable elsewhere too to turn it on/off from however many logic blocks you want.
There are many ways to do it and it all depends on what you want to do.