title: Qt widget resizes to width=256, while it shouldn't
body: <p><strong>Form setup:</strong></p>
  
  <p><code>QSplitter</code> (highlighted on the image) that contains <code>QTreeWidget</code> (left) and <code>QTableWidget</code> (right):</p>
  
  <p><img src="https://i.stack.imgur.com/RchPW.png" alt=""></p>
  
  <p>Non-default properties of these two widgets within QSplitter:</p>
  
  <ul>
  <li><p><code>QTreeWidget</code></p>
  
  <p>minimumSize / Width = 150</p></li>
  <li><p><code>QTableWidget</code></p>
  
  <p>minimumSize / Width = 300<br>
  sizePolicy / Horizontal Stretch = 1</p></li>
  </ul>
  
  <p>Basically the above setup specifies the minimum width of these two components, and that <code>QTableWidget</code>  is the one that will change it's width during form resize.<br>
  The buttons on the right side are placed in <code>QVBoxLayout</code> and it's size is fixed.</p>
  
  <p><strong>Question:</strong></p>
  
  <p>While resizing the form <code>QTreeWidget</code>'s width goes from minimum 150 up to unknown 256, and only then <code>QTableWidget</code> starts to grow, while I expect <code>QTreeWidget</code> to not grow in width at all, since <code>QTableWidget</code> is the one, that has Horizontal Stretch set to 1.</p>
  
  <p>Please note, this has nothing to do with <code>QSplitter</code>, since the same happens when I place these two widgets in <code>QHBoxLayout</code> instead.</p>
  
  <hr>
  
  <p><strong>UPDATE:</strong></p>
  
  <p>Setting <code>QTreeWidget</code> maximumSize / Width to 150 (same as minimumSize / Width) to avoid resizing of this widget gives following:</p>
  
  <p><img src="https://i.stack.imgur.com/2PMJ4.png" alt=""></p>
  
  <p><code>QTreeWidget</code> is fixed now to 150, but when the window is resized there is an empty gap between the two widgets. This gap grows up to 256-150=106, and then <code>QTableWidget</code> starts to expand.<br>
  Basically the result is similar, but this time area that was taken by <code>QTreeWidget</code> now is dedicated to this empty gap.</p>
  
  <p>I've started to feel this might be a Qt bug.</p>
  
  <p><strong>Technical info:</strong></p>
  
  <ul>
  <li>Ubuntu 10.04 (Lucid Lynx) x86_64</li>
  <li>GCC 4.4.3</li>
  <li>Qt 4.6.2</li>
  </ul>