i always put event structures in main panel. if you want nobody to fiddle with some UI buttons, then disable the buttons, not the structure. in other words, putting an event structure in a case structure is a design mistake: the event structure still capture the events, even though it will not process them. another option, is the have dynamic event registration for the 'true' case - but i think it would complicate what you try to do.
thanks....with your help i have been able to get around the second case so far but it is the first that has me wondering. When the computer is processing and does not react to user actions right away but instead after it has done its processing it will have stored all the user actions during that time period when it was frozen and then starts applying them afterwards. To be more specific i have a calculate button that turns into a cancel button when clicked. If you click on the cancel then it should cancel the calculation, however sometimes it is frozen until the calculation is finished and then it applies all the actions done by the user while it was frozen. I know I have seen this functionality on other programs so I am not so worried but again if there is anyway to avoid this........not the fact that labview freezes but the fact that it stores user actions and applies them later when i don't want to......it would be great