Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Without having the exact code, it's hard to say for sure, but having just attempted to reproduce your example, from the description above, I'd suggest looking at the following things:</p> <ol> <li><p>It sounds like you're actually calling <code>widget-&gt;height()</code> before the widget has been displayed. Instead, try calling <code>widget-&gt;sizeHint().height()</code> instead. The <a href="http://doc.qt.nokia.com/latest/qwidget.html#sizeHint-prop">QWidget::sizeHint()</a> method tells you what size the widget would <em>like to be</em>, if the parent geometry doesn't place any other constraints on it.</p></li> <li><p>If you're obtaining the <code>sizeHint()</code> and still getting the wrong answer, have a look at the documentation for <a href="http://doc.qt.nokia.com/latest/qwidget.html#ensurePolished">QWidget::ensurePolished()</a>. I believe that it's important to call this, to get more accurate geometries for widgets that have not yet been displayed:</p> <blockquote> <p>QWidget calls this function after it has been fully constructed but before it is shown the very first time. You can call this function if you want to ensure that the widget is polished before doing an operation, e.g., the correct font size might be needed in the widget's sizeHint() reimplementation.</p> </blockquote></li> <li><p>And if you're <em>still</em> having problems, then have a look at the documentation for <a href="http://doc.qt.nokia.com/latest/qwidget.html#sizePolicy-prop">QWidget::sizePolicy()</a>, and the class <a href="http://doc.qt.nokia.com/latest/qsizepolicy.html">QSizePolicy Class Reference</a>. I must admit that however many times I read the docs on <a href="http://QSizePolicy%3a%3aPolicy">enum QSizePolicy::Policy</a>, they never all sink in. It's really easy to have one incorrect size policy value mess up your layouts. </p> <p>It can be worth experimenting with the different size policies in Qt Designer, before actually applying a size policy.</p></li> </ol>
    singulars
    1. This table or related slice is empty.
    1. POFinding a QWidget's height before inserting
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USClare Macrae
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POFinding a QWidget's height before inserting
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO+1 - a height of 480 is almost certainly because it has never been displayed. The sizeHint().height() or layout->minimumSize().height() should both return the right value even before display
      singulars
      1. PO
      1. USRoger Attrill
    2. COI solved this issue about one hour after posting, but in a very ugly way... show()ing, getting the height and then hide()ing. Your way works much better, I tried it already and works. In the beginning I was accessing with `->geometry.height();` which seems the same as the one you guessed I was using. Greetings.
      singulars
      1. PO
      1. USAle
    3. COExcellent - happy to help!
      singulars
      1. PO
      1. USClare Macrae
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload