Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I started with doing everything hand-coded, and of late have been switching to using Qt Designer for most forms. Here are some benefits for each position:</p> <p><strong>Using Qt Designer</strong></p> <ul> <li>The biggest time saver for me is managing complex layouts; it saves a <em>lot</em> of tedious coding. Simply (very roughly) arrange your widgets, select them, right-click, and put them in the correct type of layout. Especially as layouts become nested, this is <em>so</em> much easier.</li> <li>It tends to keep your implementation files cleaner instead of filling them with all the boilerplate layout code. I'm type-A, so I like that.</li> <li>If you are translating your application, it is possible to send your translators the .ui files so they can <em>see</em> on your GUI where the text they are translating will be. (Assuming they are using Qt Linguist.)</li> </ul> <p><strong>Hand-coding</strong></p> <ul> <li>Control. If you have a layout where you need to instantiate / initialize the controls in a very particular order, or dynamically create the controls based on other criteria (database lookup, etc.), this is the easiest way.</li> <li>If you have custom widgets, you can kind-of-sort-of use the Designer, adding the closest built-in QWidget from which your class derived and then "upgrading" it. But you won't see a preview of your widget unless you make it a designer plugin in a separate project, which is way too much work for most use cases.</li> <li>If you have custom widgets that take parameters in their constructor beyond the optional QWidget parent, Designer can't handle it. You have no choice but to add that control manually.</li> </ul> <p><strong>Miscellaneous</strong></p> <ul> <li>I <em>don't</em> use the auto-connect SLOTS and SIGNALS feature (based on naming convention such as "on_my_button_clicked".) I have found that I almost invariably have to set up this connection at a determinate time, not whenever Qt does it for me.</li> <li>For <code>QWizard</code> forms, I have found that I need to use a different UI file for each page. You can do it all in one, but it becomes very awkward to communicate between pages in any kind of custom way.</li> </ul> <p>In summary, I start with Qt Designer and let it take me as far as it can, then hand-code it from there. That's one nice thing about what Qt Designer generates--it is just another class that becomes a member of your class, and you can access it and manipulate it as you need.</p>
    singulars
    1. This table or related slice is empty.
    1. POQt Designer vs Handcoding
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USDave Mateer
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POQt Designer vs Handcoding
      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. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWith hand-coding, there is no boilerplate layout code if you do it the right way. That is all hidden in your UI building classes. Translating is also easy as you can generate mockups with text from the same UI building classes.
      singulars
      1. PO
      1. USStephan Eggermont
 

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