Ashwini,
I don't understand what your exact problem is, but i can give you some feedback on the VI:
1) It is good to include timing into loops. But your comment implies, that you do not use timing in loops which are not connected to UI-controls. This is bad. You should always include timing into loops except if you want something (which has to be finit in execution!) to execute as fast as possible.
2) Your timing is 1s. This is far too long for proper interaction. Tests showed, that delays about some 100ms lead to misusage of the application. So please lower the time to something around 100-250 ms.
3) The VI checks "MR" against 4 and then decides if it should continue in the loop or to show the dialog. This is not good since the comparison is only done once in the beginning.
4)
Never use the "run continuous" button!
hope this helps,
Norbert
Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.