08-29-2012 04:40 PM
@smercurio_fc wrote:
To be honest, not really. The function is to write a value and generate a signaling event. It's not "only write the value if it changed".
Thanks. But I got the impression in the other way "Only trigger the event if the value is changed/true" I am still not clear. Anyhow thanks for answer and sorry for deviating the topic.
08-29-2012 04:45 PM
Yes I got it sorry for the confusion. Whatever the value that we wire to the property it is updated to the control similar to the value property additionally it triggers the event.
08-31-2012 10:03 AM
Hi Tbob, I used your block diagram but got another problem. When I press "read all", all the buttons are assisgned as "True", and they are fixed as true instead of being released. Here is the comparison of normal button operation and my current situation. Could you help me out of this?
08-31-2012 11:16 AM
That's because tbob is using the first technique I discussed in my first response. I suggest you re-read that response.
It is your responsibility to set them back to False programmatically in the event case that handles that specific button.
08-31-2012 11:52 AM
Hi smercurio_fc, thank you for your advise. I read your reply previously but not quite understand. Do you think can I implement " set them back to False programmatically" like this? Thank you!
08-31-2012 12:08 PM
YOu could use a property node Value (note this is NOT value signaling) to read the value of each control and use the returned T/F as the input to the "Value signaling" node.
That way you get the trigger but the indicated state does not change.
Ben
08-31-2012 12:15 PM
@Ben wrote:
YOu could use a property node Value (note this is NOT value signaling) to read the value of each control and use the returned T/F as the input to the "Value signaling" node.
I typically use a local variable for this, or even the actual control terminal. 😄
(We don't need the terminal inside the event anyway, because we have access to the value from the "newval" terminal)
08-31-2012 12:29 PM
@altenbach wrote:
@Ben wrote:
YOu could use a property node Value (note this is NOT value signaling) to read the value of each control and use the returned T/F as the input to the "Value signaling" node.
I typically use a local variable for this, or even the actual control terminal. 😄
(We don't need the terminal inside the event anyway, because we have access to the value from the "newval" terminal)
Agreed.
But it is is really nice to be able to double-click a control on the FP and find it and the event that is registered for it.
Ben
08-31-2012 12:34 PM
Hi Ben,
I am not quite sure about how to use property node "Value" of "read all" to read the other buttons and return T/F, could you tell me more detail about it?
08-31-2012 12:45 PM
@bhl3302 wrote:
Hi Ben,
I am not quite sure about how to use property node "Value" of "read all" to read the other buttons and return T/F, could you tell me more detail about it?
It appears that read all has mechanical action set for "latch when..."
Ben