Databases
StackOverflow2013
Postsdbo
POCreate an inspecting properties window, button driven as a JDialog
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCreate an inspecting properties window, button driven as a JDialog
    primarykey
    data
    text
    <p>What I asked originally didn't clearly state my question/problem, so I will explain it better. I have a <code>JButton</code> that sets a <code>JDialog</code> to visible. The JDialog has a <code>WindowListener</code> that sets it to NOT visible on the <code>windowDeactivated()</code> event, which is triggered anytime the user clicks outside of the dialog. The button <code>ActionListener</code> checks if the dialog isVisible, hides it if true, shows it if false.</p> <p><code>windowDeactivated()</code> will always trigger whether clicking on the button or not, as long as the user clicks outside the dialog. The problem I'm having is when the user clicks the button to close the dialog. The dialog is closed by the <code>WindowListener</code> and then the <code>ActionListener</code> tries to display it.</p> <p>If <code>windowDeactivated()</code> doesn't <code>setVisible(false)</code>, then the dialog is still open, but behind the parent window. What I'm asking for is how to get access to the location of the click inside <code>windowDeactivated()</code>. If I know that the user clicked on the button and windowDeactivated() can skip hiding the dialog, so that the button's <code>ActionListener</code> will see that it's still visible and hide it.</p> <pre> public PropertiesButton extends JButton { private JDialog theWindow; public PropertiesButton() { theWindow = new JDialog(); theWindow.setUndecorated(true); theWindow.setDefaultCloseOperation(WindowConstants.DISPOSE_ON_CLOSE); theWindow.add(new JMenuCheckBoxItem("Something")); theWindow.addWindowListener(new WindowListener() { // just an example, need to implement other methods public void windowDeactivated(WindowEvent e) { theWindow.setVisible(false); } }); this.addActionListener(new ActionListener() { public void actionPerformed(ActionEvent e) { if (theWindow.isVisible()) { theWindow.setVisible(false); } else { JButton btn = (JButton)e.getSource(); theWindow.setLocation(btn.getLocationOnScreen.x,btn.getLocationOnScreen.x-50); theWindow.setVisible(true); } } }); theWindow.setVisible(false); } } </pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USaymeric
    1. USBrian
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POCreate an inspecting properties window, button driven as a JDialog
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POCreate an inspecting properties window, button driven as a JDialog
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POCreate an inspecting properties window, button driven as a JDialog
      1. This table or related slice is empty.
      1. VTUpMod
    1. CONot sure what the question is. It looks like you seem to have figured it out. That looks right. (At first glance)
      singulars
      1. POCreate an inspecting properties window, button driven as a JDialog
      1. USjjnguy
    2. COWhat I have above will do everything I wanted, except when the clicking outside of the dialog. Clicking outside closes the dialog, which is fine, but when I click the button to open the dialog, it does not open the first time. From what I understand, the WindowListener triggers before the ActionListener and even though the dialog is NOT actually visible when the ActionListener triggers, the .isVisible() call returns a true. So, the button will .setVisible(false) even though it isn't visible.
      singulars
      1. POCreate an inspecting properties window, button driven as a JDialog
      1. USBrian
    3. COBrian, you can use a `WindowAdapter` instead of a window listener. Then you only have to implement the methods you want.
      singulars
      1. POCreate an inspecting properties window, button driven as a JDialog
      1. USjjnguy
 

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