Thanks, the horizontal stretch factor seems to get me closest to what I want.

1. Create your own class (QYourSplitterHandle) derived from "QSplitterHandle".
2. Implement:
   void QYourSplitterHandle::mousePressEvent(QMouseEvent* eventPress)
3. Create spliiter handle in your splitter class (virtual):
   virtual QSplitterHandle *createHandle();

Example:
QYourSplitterHandle* QYourSplitter::createHandle()
{
return new QYourSplitterHandle(Qt::Orientation::Horizontal, this);
}

Calculate the widths of splitter widgets attached to the current splitter and for the "snap-point"
do not call function from base class:
QSplitterHandle::mousePressEvent(eventPress);

Determine splitter handle (using splitter object):
QYourSplitterHandle* pcoSplitterHandle =
qobject_cast<QYourSplitterHandle*>(pcoSplitter->handle(0));

splitter->setSizes({20, 200, 300}) - total width of the splitter
      corresponds to 520 units
    - the left widget: (20/520) * spliter->width() - wide
    - the middle widget : (200/520) * spliter->width() - wide
    - the right widget: (300/520) * spliter->width() - wide

and if I set splitter->setSizes({0, 500, 0}) it doesn't matter what I pass 200, 500 or 1000, the left and right
widgets have a width of 0 and the middle widget has the width of the entire splitter.

I hope the logic is understandable now

Each splitter part is connected to a widget (QLabel, QListWidget, QScrollArea ....)

pcoSplitter->addWidget(pcoLeftWidget);
int iLeftViewWidth = pcoLeftWidget->width();

pcoSplitter->addWidget(pcoMiddleWidget);
int iMiddleViewWidth = pcoMiddleWidget->width();

pcoSplitter->addWidget(pcoRightWidget);
int iRightViewWidth = pcoRightWidget->widht();

If you think about this for a second you should realize this is completely illogical.

Let's say the parent widget that contains the splitter is 1000 units wide and has a splitter that has left pane 250, center 500 and right pane 250 units in width.

What would be the result of setting the splitter "sizes" (QSplitter::setSizes) to 0, 500, 0?

The space to be allotted between the three widgets is 1000. So the sizes would logically need to sum up to 1000. 0 + 500 + 0 sums to 500. Makes no sense.

pcoSplitter->addWidget(pcoLeftWidget);
int iLeftViewWidth = pcoLeftWidget->width();

pcoSplitter->addWidget(pcoMiddleWidget);
int iMiddleViewWidth = pcoMiddleWidget->width();

pcoSplitter->addWidget(pcoRightWidget);
int iRightViewWidth = pcoRightWidget->widht();

And what are the sizes? Yeah.. that's basically the meat of the question.

and to your question:
pcoSplitter->setSizes({ 0 , iMiddleViewWidth, 0 });

@SamiV123 yes it can be. You can also set the minimum size to something suitable for you.

Well yes the minimum size of a widget can be 0 but in this case it doesn't make sense since the when the splitter is at the snap point the size (width) of the widget is non-zero. So the snap point can't be at a point where the widget's minimum size is zero.. Makes sense?

Secondarily, using fixed minimum size rarely (if ever) works correctly across platforms and style engines. Using X units of width and it looks ok with Fusion or whatever? Yeah, great then go and change the style engine to kvAntum or Adwaita and see how things are all kaput because the layout and widget sizes are completely different.

Hi,

Isn't it the minimal size of the widget ?

That said, you can also use setStretchFactor so you can make have them distributed in a more suitable fashion.

The minimum size is (width) is 0. So this can't be right.

strech factor seems super obscure, doubt that will do anything other than make the situation worse.

Isn't it the minimal size of the widget ?

That said, you can also use setStretchFactor so you can make have them distributed in a more suitable fashion.