01-05-2011 02:29 PM
so the Momentary/Value Signaling is getting caught (or triggering the event) because of the timeout? but the timeout is an empty case....
01-05-2011 02:31 PM - edited 01-05-2011 02:32 PM
Try this, Fibo.
01-05-2011 02:46 PM - edited 01-05-2011 02:50 PM
No. You have a -1 connected to the timeout terminal so it never gets executed. It may as well not even be there. Try this - set momentary to true then click run. The true case will execute and the value signaling property will be written to. As soon as that happens the control is reset to false. If you now change it to true then the case structure will execute again in the true case. But not until another event in the case structure has fired.
Try something. Move the case structure and momentary button outside of the while loop. Wrap another while loop around that and run the program. This is not the right way but do it as an experiment and try to figure out what is happening. I think you will see the behavior you are expecting.
It took me a while to get my head around these things. You will have that "ah-ha!" moment before you know it and all will be crystal clear.
01-05-2011 02:55 PM
@mtat76 wrote:
Try this, Fibo.
A few notes:
01-05-2011 03:38 PM
@altenbach wrote:
@mtat76 wrote:
Try this, Fibo.
A few notes:
- if you don't use the timeout event, delete the timeout case amd value entirely.
- the "event count" indicator belongs in front of the event structure, else it will be potentially incorrect until the first event gets triggered. (We don't really care about counting the stop event ;))
Good call on the deleting of the timeout "event".
And with regards to the "we", Altenbach - personally I don't really care about counting any of the events; I already know how the structure works :o.
Muahahaha....