Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Layout problems are solved by ... LayoutManagers :-) If one doesn't what you want it to do, implement the behaviour you want. </p> <p>So if the core BoxLayout simply ignores pixels due to rounding errors, subclass and make it distribute those pixels as needed. A very raw quick example:</p> <pre><code>public static class XBoxLayout extends BoxLayout { enum Strategy { NONE, STRETCH_LAST, DISTRUBUTE } private Strategy strategy; public XBoxLayout(Container target, int axis, Strategy strategy) { super(target, axis); this.strategy = strategy; } @Override public void layoutContainer(Container target) { super.layoutContainer(target); if (Strategy.NONE == strategy) return; Insets targetInsets = target.getInsets(); int targetSize = target.getWidth() - targetInsets.left - targetInsets.right; int childSum = 0; for (Component child : target.getComponents()) { childSum += child.getWidth(); } if (targetSize &gt; childSum) { int excess = targetSize - childSum; distribute(target, excess); } } private void distribute(Container target, int excess) { System.out.println("childCount/rounding excess " + target.getComponentCount() + "/" + excess); if (Strategy.STRETCH_LAST == strategy) { Component lastChild = target.getComponent(target .getComponentCount() - 1); lastChild.setSize(lastChild.getWidth() + excess, lastChild.getHeight()); } else { int firstToDistribute = target.getComponentCount() - excess; int summedOffset = 0; for(int index = firstToDistribute; index &lt; target.getComponentCount(); index++) { Component child = target.getComponent(index); Rectangle bounds = child.getBounds(); bounds.x += summedOffset++; bounds.width += 1; child.setBounds(bounds); } } } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POJPanels don't completely stretch to occupy the available space
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USkleopatra
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POJPanels don't completely stretch to occupy the available space
      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. VTAcceptedByOriginator
    1. COThank you for your help. That does look like a viable solution, and I was looking for something involving the layout managers. The code doesn't look like it respects component size proportions (in relation with each other), even with the DISTRIBUTION strategy, but I got the point, and will try to implement something in those lines.
      singulars
      1. PO
      1. USAnoyz
    2. COI am going to second this - when you need such custom behavior, doing your own layout manager isn't that painful and you can optimize it for your specific use-case.
      singulars
      1. PO
      1. USRiyad Kalla
    3. CO@Anoyz distributing single pixels is .. a matter of strategy :-) Implement whatever you need, at the end of the day it won't be exactly proportional to actual/pref/whatever size
      singulars
      1. PO
      1. USkleopatra
 

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