Leaderboard

Name: JGCODE Preferences Dialog Library Submitter: jgcode Submitted: 30 Jan 2012 File Updated: 11 Feb 2012 Category: LabVIEW Tools Network Certified LabVIEW Version: 2009 License Type: BSD (Most common) This package is Open Source The Library contains supporting VIs that integrate with the LabVIEW Preferences Dialog to simplify file IO using OpenG VIs. Thanks to Yair/tst for help with refactoring Installation locations: <templates>\JGCODE\Preferences Page Dialog.vit - template for creating new pages <examples>\JGCODE\preferences_dialog - example application and instructions The following VIs are called dynamically so that linking is maintained: <resource>\dialog\PreferencesDialog\PreferenceDialog.vi <resource>\dialog\PreferencesDialog\optionsFrame_GetErrorReportQueue.vi <resource>\dialog\PreferencesDialog\optionsFrame_GetPageReadyNotifier.vi <resource>\dialog\PreferencesDialog\PreferencePages\SharedPrefPage_SubVIs\SetCursorBusy.vi <resource>\dialog\PreferencesDialog\PreferencePages\SharedPrefPage_SubVIs\SetCursorNormal.vi <resource>\dialog\PreferencesDialog\PreferencePages\SharedPrefPage_SubVIs\SetOkDisable.vi <resource>\dialog\PreferencesDialog\PreferencePages\SharedPrefPage_SubVIs\SetOkEnable.vi <resource>\dialog\PreferencesDialog\PreferencePages\SharedPrefPage_SubVIs\SetPanelCloseStateDisable.vi <resource>\dialog\PreferencesDialog\PreferencePages\SharedPrefPage_SubVIs\SetPanelCloseStateEnable.vi This Package depends on these other packages: oglib_appcontrol >= 4.1.0.7 oglib_array >= 4.1.0.13 oglib_file >= 4.0.0.20 oglib_variantconfig >= 4.0.0.5 Click here to download this file

The only reason I didn't try that is I assumed that taking the FP out of memory would invalidate those events? I will give it a go. Here is the Dual Loop approach - it works. All the meat is in the engine, the stuff on the Page is pretty basic (in comparison). <edit> Sweet!! It works - great suggestion The code now looks how I originally intended - reusable! </edit>

If the framework only runs the page VIs when they are put into the SP (and I'm assuming that's the case), then maybe you can try a trick - I'm assuming the Page Ready Notifier you send at the end of the Setup state tells the framework that you're done and you're ready to put the VI into the SP. What if before you do that, you open the FP (maybe hidden), then register the event, then close the FP again and only then send the notification?