Leaderboard

Since some of the old emoticons are missing, let's use this thread to hold various old and new ones. I'll start... New: | | | | | | | | Old Thread... | | | | | | | | |

I can answer the "how to create a folder" question - Get the My Computer reference from the project (probably a property), then call the "Add Item" (or whatever it's called) method on that. It accepts a string input for the type of item (probably "Folder" in your case. If you want to be sure, iterate over a tree which has folder and get the type property for each item).

Looks like a scene out of The Mummy

Did this get posted to the Bug thread ? http://forums.ni.com/ni/board/message?board.id=BreakPoint&thread.id=8320&jump=true Posting bugs anywhere and not linking to the bug thread is a lot like writting poetry on the Men's room wall. The next person that reads it may be enlightened but the world will not change because of it. If it did get posted then check the Known issues to see what the status is. Just trying to help, Ben

Here's an object diagram of my current Interface framework. Aside from some comments in the demo vi this is all the documentation I have so far. I am curious what the pain points are for others who pick up the framework and try to implement Interfaces in their own code. (Or for that matter, those who just try to understand it!) Some points to note: The Interface framework classes are highlighted in green. Everything else is extra baggage for dev work. The framework currently depends on the CollectionFramework package, highlighted in orange. Eventually I'll refactor the functionality I need into the InterfaceCollection class and remove that dependency. For now the CollectionFramework package is included in the zip file as an OpenG package. They will show up under your User palette after installation. The blue classes have been implemented for demonstration purposes. The red classes are pending implementation to fill out other demonstration scenarios. LV2009 required. Since the language of Interfaces is undefined in Labview, trying to describe things in text is difficult. I have terminology I use but sharing it right now would confuse the issue since it's not quite consistent with the diagram or the demo project. [Edit Aug 3, 2010 - Removed pre-release version. Get current version from the Code Repository.]

Create a named notifier in your splash screen. Have the splash VI wait for a notification. Acquire the notifier reference by name in the main VI. when the main VI has completed it's initialization and is 'ready', send a notification to the splash screen and then close the splash screen VI appropriately. Don't forget to set some sort of timeout on the splash VI in case your main fails to load. You can use a timeout on wait for notifier in the splash vi. Notifier Operations Functions