1) I have experimented (unsuccesfully) with the Space Start and Space End of the TestStand - Divide Space Between Panes.vi. In the original TopLevel, the FileSteps and SequenceList were being divided (right?). I didn't see how the Space Start and Space End values passed in accomplished this.
Space Start and Space End define how much space you want to divide between the N panes. Both of these are in pixels; note that you have to tell the function if you want to split horizontally or vertically by wiring a Boolean to the Vertical Splitter control. Note that there is a hard coded minimum size per pane. Don't try to put too many panes in a small area.
(2) I'm trying to re-organize the TopLevel Front Panel such that on the SequenceFile Tab, the FileSteps are at the top-left and go almost all the way down to the bottom of the tab control. At the bottom (taking up about 1/2 inch) are the TestUUTs, SinglePass, Run MainSequence buttons. To the right of the FileSteps (taking up the right 1/3 of the tab control) are the FileVariables, the SequenceList, the Threads (which I don't even want to display), and two ExpressionEdit boxes that I added to display the Descriptions of the SequenceFile and the selected Sequence. These five 'panes' go from top to bottom of the tab control and are to the right of the FileSteps. If you can picture that, how do I modify the Space Start, Space End of the TestStand - Divide Space Between Panes.vi.
I am having a bit of trouble picturing your layout, so I'm going to make some suggestions that you can use to help you whatever your layout is going to be rather than for a particular layout.
First off, I would suggest you use LabVIEW to mock up a layout- it doesn't have to be functional, what you care about is that you have a control that takes up the proper amount of space for each element. If you don't want a pane (i.e. Threads) REMOVE IT! Once you have it laid out, as you want here is a trick to find the size and position of a control: Go to the block diagram right click on a terminal and select create reference. Wire the reference into a property node and select the position and bounds All Elements and wire them to indicators then run the VI. These properties give you the top and left control coordinates and the control's width and height. Generally you will want one control to be adjacent to another- So if you have control A always on the left and it is a fixed size and three other controls B,C,and D then you would use the divide space among panes on controls B C D so that they share the remaining space. Space Start would be the A.left + A.width and the end space would be the right side of the tab control (or the screen) i.e. tab.left + tab.width. I would recommend against hard coding constant values- if you want 1/3 or the screen calculate it form the screen size. You never know when you will need to change screen size!
Repeat this process for panes that are tiled vertically as well, but use tops and height instead of left and width.
The next part of the process is to decide which (if any) borders you would like users to be able to drag. This can be set by right clicking on the control (say the sequence File View) and selecting Sequence View -> Properties... a dialog appears with several tabs, select Borders and select which of the borders you want to allow dragging on (Top. Left, Bottom, or Right). Note that when two panes are adjacent only one of them needs to have a dragable border to allow the user to resize both. You will need to create a callback VI to handle the drag events and add it to the Reg Event Callback in Full UI - Configure Event Callbacks.vi. If you uncheck dragging or separate panes by adding a pane between them you should remove the unused border drag callback from Reg Event Callback in Full UI - Configure Event Callbacks.vi.
-Rick Francis
