Are you seeing two sets of window decorations on JDialogs in Tiger
beta 1 (Sun) if you turn decorations off and then ask Swing to provide
them? If so, please vote for bug 490:
http://developer.java.sun.com/developer/bugParade/bugs/490.html
This is with KDE 3.1.1; there's code in the bug r
Glenn Holmer <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] wrote:
>> There is a bug report in the JDC Bug Database concerning window
>> management problems with KDE (4392053). It's second in the Top 25
>> Bugs with 335 votes. According to the evaluation KDE is not a
>> supported configuration
[EMAIL PROTECTED] wrote:
> There is a bug report in the JDC Bug Database concerning window management
> problems with KDE (4392053). It's second in the Top 25 Bugs with 335 votes.
> According to the evaluation KDE is not a supported configuration. So if
> things don't work, tough.
[from the bug
Oktay Akbal wrote:
> There seem to be several issues with modal JDialogs in 1.4-final.
> Some (?) of them do not show up in -beta2.
> We have a Problem with blank Dialogs and hanging Application that
> does not only show up under KDE.
>
> Is it possible for you to test beta2
There is a bug report in the JDC Bug Database concerning window management
problems with KDE (4392053). It's second in the Top 25 Bugs with 335 votes.
According to the evaluation KDE is not a supported configuration. So if
things don't work, tough.
Just another instance of Sun's idiotic attitud
There seem to be several issues with modal JDialogs in 1.4-final.
Some (?) of them do not show up in -beta2.
We have a Problem with blank Dialogs and hanging Application that
does not only show up under KDE.
Is it possible for you to test beta2 ?
Oktay
On Fri, 5 Apr 2002, Glenn Holmer wrote
> Does anybody know why this might be and if there's a workaround?
> KDE has always been our standard, so we'd rather not switch.
I am the total newbie round here, but did you delete kaffe -
someone told me that was a good idea?
Walter
--
Walter Logeman
Psychotherapist
http://www.psybernet
We're evaluating JDK1.4 here, and find a serious issue with KDE.
Many of our Java apps start by showing a setup dialog, and the way
they usually do it is by listening on windowActivated for the main
JFrame. That handler checks a first-time-thru flag, and if true,
shows the modal dialog.
What we
I'm seeing a couple of problems with modeless dialogs.
1. These dialogs are "stuck" to the parent window. i.e. when you move the
parent frame the dialog moves too.
2. If you minimize the parent window, the dialog minimizes with it, and it
you then bring the window back up th
I apologize if this is in the FAQ, but I am unable to currently access
it, so I seek the wisdom of the list...
I have been having trouble with modal dialogs in Swing. In particular,
the parent window is allowed to get focus after it has popped up a modal
dialog. I would like the behavior of
Hi All!
I didn't find an answer in the mail-list archive [ :-> ], so, I'll ask:
I'm working on a java application that uses several JDialog boxes. If
I use the constructor with params within my extension of JDialog (i. e.
super(dad, title, modal); ), the JDialog does not have a title bar
False Alarm.
After closer examination (thanks to Juergen), I realized that I fired
a false alarm.
--
Dimitrios Vyzovitis -- Information Processing Laboratory
[EMAIL PROTECTED] -- Aristotle University of Thessaloniki
[EMAIL PROTECTED] -- Dept. of Electrical and Computer Engineering
> Dimitris Vyzovitis writes:
>> I wrote a short program and tested it with 1.1.7, 1.2 (both with
>> green and native threads) on Solaris and with 1.1.7 (green threads
>> and native threads) and 1.2 native threads (not available yet) on Linux:
>> All show the same behavior -- t
ake a closer look
at this?
OK, I'll try to clean up unecessary stuff because there are a lot of dependencies
between packages I use.
Note that we are talking about modal dialogs but your posted example
creates a *non*-modal dialog:
> public NoiseWizard( Component master, NoiseBuilder bui
olaris and with 1.1.7 (green threads
and native threads) and 1.2 native threads (not available yet) on Linux:
All show the same behavior -- the execution stops after show().
Where does the execution stop on windows? After the finishing the
execution of the topmost constructor?
Could you please se
Juergen Kreileder wrote:
> Dimitris Vyzovitis writes:
Dimitris> Hi everyone,
Dimitris> It appears there is a nasty bug in a modal
dialog's
Dimitris> construction process. If I subclass
a modal dialog that
Dimitris> appears in its constructor (ie the constructor
ends with
> Dimitris Vyzovitis writes:
Dimitris> Hi everyone,
Dimitris> It appears there is a nasty bug in a modal dialog's
Dimitris> construction process. If I subclass a modal dialog that
Dimitris> appears in its constructor (ie the constructor ends with
Dimitris> the typical pac
More on the subject:
This behavior doesn't appear if I use the -native switch!
Perhaps it is a green_threads glitch...
--
Dimitrios Vyzovitis -- Information Processing Laboratory
[EMAIL PROTECTED] -- Aristotle University of Thessaloniki
[EMAIL PROTECTED] -- Dept. of Electrical and Computer
Hi everyone,
It appears there is a nasty bug in a modal dialog's construction
process.
If I subclass a modal dialog that appears in its constructor (ie the
constructor ends with the typical pack(); show(); setResizable( false );
),
the subclass constructor doesn't get called unless the dialog is
d
eparator _
Subject: Re: Dialogs in applets
Author: welzel ([EMAIL PROTECTED]) at lon-mime
Date:02/12/98 05:23
I saw a message a while back in the list about using modal dialogs in
Applets. I just want to get a Dialog to work in an applet and could use
some advice. The con
I saw a message a while back in the list about using modal dialogs in
Applets. I just want to get a Dialog to work in an applet and could use
some advice. The constructor for a Dialog wants a Frame. How do I get a
Frame from a JApplet?
Some documentation I had suggested using the getParent
Travis Winfrey wrote:
>
>
> This could be a basic bug in JDK, but invisibile dialogs
> frequently are caused by simple sizing bug in your dialog
> instance. Check to make sure they have a reasonable
> minimum size -- the relationship to the resizability attribute
> migh
Juergen Kreileder wrote:
> It should work if you first open the dialog resizable and then
> set it non-resizable.
>
Nice hack.
The workaround works, I can have my dialog not resiable in KDE.
Thanx!
Dimitris
> Has anybody observed something similar?
> Is there a bug in1.1.7 (possibly related to a KDE bug) thathas to do with dialogs?
> I remember that there was an issue of resolving some resizability bugs with Dialogs
>in this release. but it seems
> that it might have introduced some
> Stewart Allen writes:
Stewart> I have also noticed some GUI glitches with 1.17. None of these
Stewart> exist in 1.16. My environment is WindowMaker on RedHat 5.2.
Stewart> 1) Button-clicks sometimes leave a button
Stewart> "depressed". You have to click it a second ti
n1.1.7 (possibly related to a KDE bug) thathas to do
> with dialogs?
> I remember that there was an issue of resolving some resizability bugs
> with Dialogs in this release. but it seems that it might have introduced
> some obscure issues... At least imy dialog is not resizable
re in .6)!!!
Dimitris> And -guess what... If I make the dialog resizable - no
Dimitris> call to setResizable- my dialog appears - as if by
Dimitris> magic...
Dimitris> Has anybody observed something similar?
Dimitris> Is there a bug in1.1.7 (possibly relate
related to a KDE bug) thathas to do
with dialogs?
I remember that there was an issue of resolving some resizability bugs
with Dialogs in this release. but it seems that it might have introduced
some obscure issues... At least imy dialog is not resizable - if it ever
appears.
I woudl appreciate any
28 matches
Mail list logo