Thanks! That gives me enough know how to do everything I want - I even
added another splitter for the top/bottom - it's fantastic - already
have been able to improve on the original UI - it now scales more nicely
and displays more info easily at high resolutions (I have a 28in
monitor, and this is very important to me).
- Mark
On 9/16/10 10:35 AM, Greg Brown wrote:
> I think the problem may be the outer BoxPane, the one that is a direct child
> of the TablePane.Row.
>
> Rather than using a vertical BoxPane here, I'd suggest creating multiple
> table rows, one for each component you currently have in the box pane. Give
> the first three the default height ("-1") and the last one (which contains
> the split pane) a height of "1*". That will allow the split pane to fill the
> remaining vertical space.
>
> G
>
> On Sep 15, 2010, at 10:33 PM, Mark Miller wrote:
>
>> So now that I have everything going great horizontally ... any tips on
>> my vertical problem? The split pane seems to want to go to height 0
>> unless I give it a specific preferred height. Putting it in a Boxpane
>> with horizontal orientation and fill:true doesn't seem to want to
>> stretch it out either. Nor does sticking a border around it - my naive
>> attempts at getting this to work so far...any tips?
>>
>> Thanks so much for the great help,
>>
>> - Mark
>>
>>
>> On 9/15/10 8:11 PM, Greg Brown wrote:
>>> I think I see the problem. You are using a BoxPane as the tab component. By
>>> default, box panes are horizontally-oriented. When "fill" is set to true, a
>>> horizontal BoxPane will fill in the vertical direction. However, you want
>>> to fill in the horizontal direction. Changing the orientation to vertical
>>> (and maintaining the fill style) would probably resolve your layout issue.
>>> However, a simpler fix would be to simply use the Border as the tab
>>> component and eliminate the BoxPane (a Border always stretches its content
>>> to fill the entire client area). Let me know if that doesn't work.
>>>
>>> By the way, your app looks great! Can we expect to see Lucene using Pivot
>>> in the near future? ;-)
>>>
>>> Greg
>>>
>>>
>>
>