LabVIEW
Disabled button fires events to event structure
@rrawer wrote:
to apoc:
Just one remark to the code you posted - the Delta t was not designed to show the time between the two events but to show that in the case posted originally the time property on the left of the event structure did not give me the point of time where the button was pressed but the point of time the event was actually executed (due to the tagged Lock front panel property...)
Well, nobody with the name of apoc contributed to this thread and apok did not post code with time indicators, so you are probably talking about my code. You never really explained what you are trying to show with the the deltaT indicator (note that you can show the digital display of the chart, eliminating the extra terminal), so I took a wild guess. If you want to show the time between the event trigger and event execution, you can of course use the attached modification. In any case, the flavor of timing display seem irrelevant to the problem you are trying to demonstrate.
@rrawer wrote:
to apoc:
Thanks - you are correct. I wasn't aware of that the Lock front panel property actually only delays the execution of the events - I thought they would be ignored which explains why I didn't expect the behavior...
Again, are you talking about my explanation here? It the problem solved now?
@rrawer wrote:
I wasn't aware of that the Lock front panel property actually only delays the execution of the events - I thought they would be ignored which explains why I didn't expect the behavior...
I believe this is documented in the event structure. This is why the consumer/producer follows the programming paradigm of not doing anything in an event structure that takes significant amount of time. If you have a task that will take time, don't just freeze the UI so that the user will keep clicking but pass it off on a queue to an execution loop.
It appears that the code functions as expected.
