TPairsplitter could be better but limited currently.

[jamie]

Unless I missed something I cannot widen the TPairSplitter so I can have left right arrows and things like it being parented and owned by the splitter in the middle.

  I can and did do this using a single splitter but had to do all the other special anchoring to get things to work, but in the end its done, just a lot more work than needed if the TPairsplitter would accept controls and is width sizable to facilitate the action.

 Any thoughts on this, I was also thinking of a movable fancy toolbar.

Jamie

[wp]

I don't understand what you mean. But the attached demo is working as I would have expected.

[Hansvb]

I think what is meant is that with a pairsplitter you can't make the splitter beam wider. That is not a property. But you can imitate a pair splitter. Then you can adjust the width of the splitter bar.

[jamie]

@WP

You can use a single TSplitter in design mode to drop controls on the actual splitter thus the splitter is able to widen or grow higher to allow for client space so you can apply child controls on it. A good example of this would be using LEFT / RIGH arrows on the splitter to indicate data items that can be moved back and forth. or Buttons to clear a list on either side and all of this lives on the actual splitter.

 with a TPairSplitter, it's still a single TSplitter but there are no design abilities to enlarge the splitter client's area to drop controls on it at design time.

Jamie

[jamie]

No traction on this yet?

Jamie