Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Here is code that renders with an outside Thread doing all the work. It does this by being able to render anything that implements the <code>Renderable</code> interface. I have tested this with both Swing and AWT (<code>JFrame</code> and <code>Frame</code>) and it works with no flickering. Note, it does flicker if you implement onto a <code>JRootPane</code> and set that pane as the <code>JFrame</code>'s root pane. This has to do with how the component is buffered, and could be fixed if that is how you want to use this.</p> <p>If this is still not what you were looking for, just say and I'll give it another go. This is actually fun, as it has been awhile since I've done any Java GUI work.</p> <p>Anyways, here you go:</p> <pre><code>import java.awt.Color; import java.awt.Dimension; import java.awt.Frame; import java.awt.Graphics; import java.awt.Toolkit; import javax.swing.JFrame; public class SmoothResize extends Frame implements Renderable { public static void main(String[] args) { Toolkit.getDefaultToolkit().setDynamicLayout(true); System.setProperty("sun.awt.noerasebackground", "true"); SmoothResize srtest = new SmoothResize(); RenderThread renderThread = new RenderThread(srtest); renderThread.start(); srtest.setSize(100, 100); srtest.setVisible(true); } public SmoothResize() { } public void addNotify() { super.addNotify(); createBufferStrategy(2); } @Override public Dimension getSize() { return new Dimension(getWidth(), getHeight()); } @Override public Graphics acquireGraphics() { return this.getGraphics(); } } class RenderThread extends Thread { Renderable target; Dimension last_size = new Dimension(Integer.MAX_VALUE, Integer.MAX_VALUE); public RenderThread(Renderable d) { if (d == null) { throw new NullPointerException("Drawable target cannot be null."); } target = d; } @Override public void run() { while (true) { render(false); } } private synchronized void render(boolean force) { Dimension size; do { size = target.getSize(); if (size == null) { return; } Graphics draw = target.acquireGraphics(); if (draw == null) { return; } draw.setPaintMode(); int w = (int) (((double) (size.width)) / 2 + 0.5); int h = (int) (((double) (size.height)) / 2 + 0.5); draw.setColor(Color.YELLOW); draw.fillRect(0, h, w, h); draw.fillRect(w, 0, w, h); draw.setColor(Color.BLACK); draw.fillRect(0, 0, w, h); draw.fillRect(w, h, w, h); draw.dispose(); // Repeat the rendering if the target changed size } while (!size.equals(target.getSize())); } } interface Renderable { public Graphics acquireGraphics(); public Dimension getSize(); } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POAWT custom rendering - capture smooth resizes and eliminate resize flicker
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJosh
    1. USJosh
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POAWT custom rendering - capture smooth resizes and eliminate resize flicker
      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
    1. COThat looks pretty neat. I shall try it out ASAP (which unfortunately may be Monday if I can't get to it tonight). A quick question though - the Renderable interface is just something locally defined, right? (No java.awt.Renderable or similar seems to exist.)
      singulars
      1. PO
      1. USCharles Goodwin
    2. COI won't be using a rootpane, as the custom UI we use takes over everything so it isn't necessary AFAICT.
      singulars
      1. PO
      1. USCharles Goodwin
    3. COThe `Renderable` interface is defined as an inner class at the bottom of the file. It seemed to me using an interface was the best way to do it, as it provided the most flexibility to your implementation.
      singulars
      1. PO
      1. USJosh
 

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