Re: Class Loading on Different Opperating Systems
- From: "Steve W. Jackson" <stevewjackson@xxxxxxxxxxx>
- Date: Fri, 31 Mar 2006 12:47:17 -0600
In article <MPG.1e970ebba46a21d8989e1c@xxxxxxxxxxxxxxxx>,
Chris Smith <cdsmith@xxxxxxx> wrote:
[ snip ]
I still find it hard to believe that WindowListener.windowClosing
doesn't work properly on the Mac... but if you've tried it, I guess I
can't argue since I don't have a Mac to try it with.
WindowListener.windowClosing works exactly the same way on a Mac as it
does in Windows and Linux.
The origins of this question are not about handling window closing
events, but about the proper way when running on a Mac to handle the
system-provided Quit and About menu items. If you took a Swing app you
designed on Windows or Linux and moved it to a Mac, you would find those
items present whether you wanted them or not. And the Quit menu item,
since your app wouldn't provide any handling for it, would simply
unceremoniously terminate your application without your intervention.
The About item would display a simplistic dialog with "Java" in it
rather than using your already-built code.
= Steve =
--
Steve W. Jackson
Montgomery, Alabama
.
- References:
- Class Loading on Different Opperating Systems
- From: Rationem
- Re: Class Loading on Different Opperating Systems
- From: Chris Smith
- Class Loading on Different Opperating Systems
- Prev by Date: Re: Why is JAR so slow?
- Next by Date: Re: JavaDojo - Exceptional beta till end of May 2006
- Previous by thread: Re: Class Loading on Different Opperating Systems
- Next by thread: Re: Class Loading on Different Opperating Systems
- Index(es):
Relevant Pages
|