qmicron Posted September 30, 2006 Report Share Posted September 30, 2006 How programmatically fire the "panel close?" event ? Quote Link to comment
pallen Posted October 1, 2006 Report Share Posted October 1, 2006 How programmatically fire the "panel close?" event ? There was a discussion here: http://forums.ni.com/ni/board/message?boar...id=60156#M70366 On using the invoke node to close a front panel. Quote Link to comment
Aristos Queue Posted October 1, 2006 Report Share Posted October 1, 2006 How programmatically fire the "panel close?" event ? With the exception of "Application Exit" (in Lv8.2) and user defined events, no events of the Event Structure can be triggered programmatically. If a panel is closed programmatically, that does not fire a Panel Close event. This is important for VIs that filter the panel close event, then do some clean up work and then close their own panels (or do the same on behalf of another VI). Similar applies to Value Changed (where the value gets changed, and in the event code the value is somehow modified [perhaps pinned to be within a certain range] ). The system breaks down if the programmatic work triggers events. App Exit was added as an exception predominantly because it *can't* trigger itself (once LV is exiting, its exiting!) and it provides a way for VIs to guarantee a time to do their clean up work (such as resetting hardware) for built applications. Quote Link to comment
Yair Posted October 1, 2006 Report Share Posted October 1, 2006 With the exception of "Application Exit" (in Lv8.2) and user defined events, no events of the Event Structure can be triggered programmatically...Similar applies to Value Changed (where the value gets changed, and in the event code the value is somehow modified [perhaps pinned to be within a certain range] ). The system breaks down if the programmatic work triggers events. Except that we do have the capability to fire the Value Change event programmatically. Sure, we have to select the right property first, but it can be done, so why shouldn't we be able to have another option for that method called "Fire event?" and choose to use it when WE want to? BTW, I'm not saying this should be done, just that it could be done and that it might not be a bad idea. Since we can't use a user event in the same case as a filter event and since (presumably) the loop would stop after the case executes, this doesn't leave users with much of a choice for how to do this programmatically other than duplicating their cleanup case. Quote Link to comment
qmicron Posted October 1, 2006 Author Report Share Posted October 1, 2006 Thanks for clearifying. Quote Link to comment
Ton Plomp Posted October 2, 2006 Report Share Posted October 2, 2006 Thanks for clearifying. Well I think it is theoretically possible (correct me if I'm wrong) But what if you use a win32.dll call to close the window? I think this will trigger the event! (Win only offcourse and not pure G) Ton Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.