The patch below takes three values that have to meet a condition.
it is then packed in a list. What I am expecting is to get the value 111 to test true. What happens looking at the print results is that the value can be 110 and for some reason the equal to condition function will say true!?
No sure whats going on there is the logic working differently from programmes such as c or python?
Many thanks
-
PD Logic conditions
-
ive tried using the sel 1 object but when I press one of the other buttons on the grid a bang for some reason still gets through?
-
@Fauveboy Putting [change] before [sel 1] could solve this.
Also with [change] you wouldn't need [sel] and bang anymore, i guess.
-
@ingox fraid not...the button toggles on but when any other one is pushed it swtiches off and vis versa
-
@Fauveboy Ah ok, i thought this would be the desired behavior. If you want it to toggle only once and never again after this you can use this switch:
Obviously you can open the spigot again if needed by sending 1 to the right inlet. -
I think i got you wrong. This might be what you are looking for: I changed the order of the receives so now the results of x and y will be stored in the expression object, but only s will trigger the hole thing.
-
@ingox said:
@Fauveboy Ah ok, i thought this would be the desired behavior. If you want it to toggle only once and never again after this you can use this switch:
Obviously you can open the spigot again if needed by sending 1 to the right inlet.thanks. this solved my problem in the experimental mouse plugin thread. interesting ideas.
-
Just to continue extending logic musings here.... numbers larger or equal to 12 still get through the gate which i imagine to be closed when equal to 15 is false?