You may need to provide a little more information. I know that I have
successfully used JOptionPane and JDialogs both before and after creating
EmbeddedSwingComposites. The code I am working from is modified from
Gordon's original article code.
Originally I was often having this problem when an invisible dialog was
added to the SwtInputBlocker... but I believe the fix for that one has since
been applied to the sample code.
I would also suspect that you are getting pop-under windows (your swing
window could be trapped behind your SWT Window) but it is hard to say. You
could also try the changes Gordon and I discuss in the September 19th post
to this group.
In short, I would hazard a guess that compatibility issues such as this are
vital to the project and will eventually be worked out.
-James
"Cklewis" <chriskwonlewis@xxxxxxx> wrote in message
news:fgg8p4$5ko$1@xxxxxxxxxxxxxxxxxxxx
Will there be a fix for letting you use JOptionPane and JDialogs(etc) ?
I noticed if I use JOptionPane BEFORE creating my EmbeddedSwingComposite
it works just fine. But if I attempt to use JOptionPane or a JDialog
after I've created the EmbeddedSwingComposite that it will display, but
it tends to freeze the whole program.
Not sure if you were aware of this problem, but it would be nice to be
able to use JOptionPane, and in my case a JDialog since the person
before me wrote a lot of code for that particular section which uses a
JDialog and JTrees. Initially i thought the problem was setting the
JDialog's frame owner to the awt frame in EmbeddedSwingComposite. But I
experimented with a regular JOptionPane(doesn't ask for the parent
component/frame) and noticed the same problem.