i trying to debug the program, and i realise that the event structure will hang the program is if i click the button that event structure detecting fast, it will hang and stopped there...
is this a bug or what? even i place a time delay in it also no use... the event is mouse down for button
By the VI "hanging", do you mean that the VI keeps on running and that you are not able to stop it? If so, please make sure that you have an event case for the stop button that would stop the while loop.
If the above suggestion does not help or if I am not correctly understanding your issue, please reply to this post with your comments. Could you also post a simplified version of your code demonstrating the problem?
Fatal Internal Error : "window.cpp", line 2978 LabVIEW version 7.0 You will lose any unsaved work, For assistance in resolving this problem, please relauch LabVIEW, or contact National Instruments.
above error might appear or VI will hang, if user click the button fast... and may I know, is there anyway to make the button recover to false value when the event start
I played a bit with your VIs and made a few changes. Please find the modified VIs attached. Basically there was something going wrong with the events queuing up with mouse down events. I changed the "mouse down" events to value change and made a few other changes.
Please see if the modified VIs work as expected. If you have more questions, please feel free to post your comments.
Hello, They are v7.1 VI... I can't open them with v7.0 I changed the events to mouse up, so they will not in true stats when or after the event execute, so i don't need the property node to change value too... i realise that window.cpp error, line 2987 is not a new problem... have NI solved the problem? =]
I apologize for the oversight. Please find the attached VIs (now converted to LV 7.0). Apart from changing the "mouse down" event to "value change", I have also changed the mechanical action of booleans to "latch when pressed" . This would change the value of the button only during the duration it is pressed. As soon as it is released, the value of the button will revert back to its default value('false' in our case) so we dont need to change the value of the button inside the event case.
Windows.cpp error in Line 2978 has indeed been reported to National Instruments. The LabVIEW R&D team is investigating the error.