Leaderboard

On a side note: if you are going to populate it with a lot of items (hundreds) it might be an idea to not fill it all in one go. Add child items on demand instead, i.e. when a node is expanded (use the "Item Open" filter event to intercept). Otherwise population of the native tree control can be extremely slow and make the GUI abnormally unresponsive.

How about this?

"Natural starting point" is not as obvious as it seems to be. We have to distinguish visual starting point and real starting point. Real one is always in the center of terminal (rectangle visible on connector pane). Visual is in the place where it goes out from below the icon. The little piece between these points is not visible, but it is always present and it influences behavior of the wire when you move icon around. If you want to determine nice "natural starting point" (in visual terms), you have to consider also shape of the icon - as it may be smaller then 32x32 square. Shape of the icon is determined be "outermost" spot of white pixels (it becomes transparent). So determination of object's borders is not so trivial... Doable. We have to store original shape somewhere (tags are natural place for such a data) and to introduce "Revert shape" command. Doable and simplest of features you proposed. Another nice point for scripting practice

Chris, that could be solved if you right click on the property node and select this option: ...but of course you need to have LabVIEW 2013 Alpha installed

Calling the SetCurrentDirectory() Windows API with a path you do not mind to be locked. The issue is that the Common File Dialog function in Windows sets this to the current path whenever it is dismissed with an OK click. So yes it is really a Windows issue. It happens with other applications too, that use the Common File Dialog but you rarely run into that issue there, at least I don't. The actual API seems to have a flag OFN_NOCHANGEDIR that prevents Windows from changing the current directory if the user browses to a different directory during the dialog, but it is not supported before Vista. So NI still would have to inmplement a workaround around the Common File Dialog call, which admittedly shouldn't be difficult, but it may have implications in areas nobody is thinking about at the moment. The other issue with files being locked by LabVIEW that another application opened I'm flabbergasted. Never saw that happen so far.