In addition to what has been said before, you could check Jira for
keywords jfxpanel and/or swing. Just today we had another Mac-only
problem. Apparently AWT is not as thread-safe on Mac as it is on
Windows, resulting in deadlocks in native AWT code (which currently is a
guess, not confirmed,
On 06/17/13 16:35, Werner Lehmann wrote:
In addition to what has been said before, you could check Jira for
keywords jfxpanel and/or swing. Just today we had another Mac-only
problem. Apparently AWT is not as thread-safe on Mac as it is on
Windows, resulting in deadlocks in native AWT code
On 6/17/2013 5:17 PM, Anthony Petrov wrote:
On 06/17/13 16:35, Werner Lehmann wrote:
In addition to what has been said before, you could check Jira for
keywords jfxpanel and/or swing. Just today we had another Mac-only
problem. Apparently AWT is not as thread-safe on Mac as it is on
Windows,
Also seen today: after closing the last JFXPanel while the Swing
application continues, FX would exit the platform (not the VM) and you
cannot use another JFXPanel. There is probably some workaround available.
You want to call Platform.setImplicitExit(false). Please see
On Sat, Jun 15, 2013 at 11:39 PM, Pedro Duque Vieira
pedro.duquevie...@gmail.com wrote:
My biggest problems were with having 2 UI threads.
I ran into some concurrency issues between the 2.
Meaning things that just needed extra care or things that were hard to
work around? Could you elaborate a
Hi,
we're currently in the process of migrating our Swing application from
Apple JDK 6 to OpenJDK 8 hoping to be able to ship it bundled with
OpenJDK 8 in the coming months. In addition to that we're seriously
considering a Migration of the UI to JFX and it appears very tempting
to do this
