Fixed issues #1 and #2.

[qalldredge]

VI information keeps track of its own application instance in order to load the BD and to open the file. This way the application instance that VI Peek runs in is irrelevant. This will enable VI Peek to run in whatever context if it needs to run in a NI internal context (i.e. launched from right-click menu, Quick Drop Keyboard Shortcut, and/or Tools menu, or if it can be run in place of the Navigation window).

I also split the UI into panes for better resizability and added a status bar at the bottom that displays the current application instance that the displayed VI is in.

[qalldredge]

Also, fixed issue #4. The Peek window will resize to the BD contents. No limit was placed on how large this could get. That might want to be considered for another feature/issue.

[jacobson3]

Thanks for taking a look at this. I didn't think you could insert the block diagram of a VI that was in a completely different application context but everything seems to be working as expected. Some comments on the commit:

• I'll close out 4 but I think I envisioned more of a "size-to-fit" where as this just shows the default view (the view you would see if you just opened up the block diagram. Overall I'm not sure which style I would like better. I'm leaning towards your implementation because it probably more closely represents what the user would want to see.
• When pinning the peek window the window won't resize. I'm not sure this would even be a bug though (wasn't a corner case I had even thought of).
• I'm pretty neutral to displaying the application context but seeing as it's additional functionality I'll keep it for now.