LabVIEW
Event problem, control does not working
OK, take a few steps back and look at your code from scratch! 🙂
You seem to be under the false impression that a tab control needs a case structure on the diagram. Don't micromanage your code! A tab structure is just an easy way to simplify the front panel. From the perspective of the code, you can assume that all controls of all tabs are always visible. (If execution should depend on tab position, place the case structure inside the event structure. ;))
See also my earlier comments here.
You should never place event structures inside cases (or even worse, multiple event structures in multiple cases of the same case structure). Having to add unecessary timeouts is just a kludge to hide a poor program design. More comments can be found at the end of my other post.
Don't add timeout events unless you really need to do something important at regular intervals. Most of my event structures don't use the timeout event at all.
Also, if a stop button should be accessible independent of tab position, it should probably NOT be on the tab structure, but next to it! 🙂 Alternatively, you can "float" a single stop button on top of the tab structure as follows: Select the stop button, then, using only the arrow keys, move it to the desired location on top of the tab structure. While editing, the stop button will have a shadow to indicate that it is not part of the tabs. This shadow disappears while running.
You seem to be under the false impression that a tab control needs a case structure on the diagram. Don't micromanage your code! A tab structure is just an easy way to simplify the front panel. From the perspective of the code, you can assume that all controls of all tabs are always visible. (If execution should depend on tab position, place the case structure inside the event structure. ;))
See also my earlier comments here.
You should never place event structures inside cases (or even worse, multiple event structures in multiple cases of the same case structure). Having to add unecessary timeouts is just a kludge to hide a poor program design. More comments can be found at the end of my other post.
Don't add timeout events unless you really need to do something important at regular intervals. Most of my event structures don't use the timeout event at all.
Also, if a stop button should be accessible independent of tab position, it should probably NOT be on the tab structure, but next to it! 🙂 Alternatively, you can "float" a single stop button on top of the tab structure as follows: Select the stop button, then, using only the arrow keys, move it to the desired location on top of the tab structure. While editing, the stop button will have a shadow to indicate that it is not part of the tabs. This shadow disappears while running.
