On Thu, 8 Feb 2001, Martin, Stephen wrote:
> I have a situation right now where I am experienceing it more often than not
> when
> trying to bring up a JOptionPane. I've tried a number of things, such as
> making sure that
> I do in the SwingEvent Thread, making sure I do it not in the Swing event
> thread, calling yield
> before i create the dialog, all with the same result.
>
> I then switch to the IBM 1.3 jdk and have not experienced the problem. I
> thought that this might
> indicate that hotspot is to blame so I went back to the Blackdown jdk and
> tried it with -Djava.compiler=none
> but it still happens.
I am a linux geek and I regularly see this sort of behavior in apps
written by inexperienced Java developers running windows. It seems that
the heavyweight peers behave differently between *nix and Windows. Some
actions which are separate method calls in Java are hardcoded in Windows
peers.
For instance, the action of de-iconifying a window does NOT automatically
bring that window to top in a *nix window manager, so the method must be
called to force it to the top. On Windows, de-iconifying a window
brings it to the top automatically.
So, many Java apps developed on Windows and not tested on *nix will
behave oddly because necessary Java calls were not made.
Generally, when I see a window misbehaving as yours are, I start looking for
a missing call to pack() or validate() or invalidate() or whatever.
Inserting those where they are needed generally makes my dialogs behave
on all platforms, not just Windows.
I don't know that this is the issue you're having, but it's where I
start looking.
--
Joi Ellis Software Engineer
Aravox Technologies [EMAIL PROTECTED], [EMAIL PROTECTED]
No matter what we think of Linux versus FreeBSD, etc., the one thing I
really like about Linux is that it has Microsoft worried. Anything
that kicks a monopoly in the pants has got to be good for something.
- Chris Johnson
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
