🚀 go-pugleaf

That's true, the dialog is modal, but there are cases where, if the parent
frame is null, you can still bring Frame1 to the foreground, even though
nothing else (menus, buttons, etc.) will respond.  It can be a real nuisance
for users, so you should always, wherever possible, assign a parent to a
dialog.

-- 
Check out our latest white papers at
http://www.datadevelopment.com/papers/index.html

BladeNET Scores With Borland Enterprise Tools
Team Development with JBuilder and Borland Enterprise Server

Dolphin Data Development Ltd.
http://www.datadevelopment.com/

"Ron" <rgans@nospamRonaldgansphotographyDOTcom> wrote in message
news:4051bcf9$1@newsgroups.borland.com...
> Admittedly, I am a novice at this (but a C++ and VB programmer for about
20
> years), so  I may be doing something wrong, but I just tried it and the
> JOptionPane was definitely modal to the the Frame:
>
> here's the code I wrote:
>
>
> public class Frame1 extends JFrame implements WindowConstants {
>   //Construct the frame
>   public Frame1() {
>     super ("Focus Frame");
>     setSize(400,400);
> //...code where a series of JInternalFrames are created is omitted....
>
>  WindowAdapter a = new WindowAdapter() {
>       public void windowClosing(WindowEvent e) {
>         int confirm = JOptionPane.showOptionDialog(null, "Really exit?",
>             "Exit Confirmation",
>             JOptionPane.YES_NO_OPTION,
>             JOptionPane.QUESTION_MESSAGE,
>             null, null, null);
>         if (confirm == 0) {
>           //Frame1.dispose();
>           System.exit(0);
>         }
>       }
>     };
>
>   addWindowListener(a);
>  }
>   public static void main (String[] args) {
>     Frame1 frame = new Frame1();
>     frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
>     frame.setBounds(0,0,600,450);
>     frame.setVisible(true);
>   }
>
> When I run this, and try to exit (via the Java cup icon in the top left)
the
> exit dialog is definitely modal.
>
> RON
>
> "Tor Iver Wilhelmsen (TeamB)" <tor.wilhelmsen@ergo.no> wrote in message
> news:u8yi632td.fsf@ergo.no...
> > "Ron" <rgans@nospamRonaldgansphotographyDOTcom> writes:
> >
> > > Thanks! I tried it and it worked, but then the question: I used null
and
> > > that worked also. Both Frame1.this and null seem to have the same
> > > functionality, in this very tiny example.
> >
> > It does - until you bring the frame to the foreground. If you have
> > passed the frame to JOptionPane, the modal dialog will then pop to the
> > foreground; otherwise the modal dialog remains in the background and
> > the user will not know why they can\t interact with the frame.
>
>