|Re: Requirements to use FXCanvas in Eclipse plugins? [message #1768698 is a reply to message #1766938]
||Fri, 21 July 2017 18:30
| Theodore Murdock
Registered: January 2015
We do gain something from the exercise, because SWT/AWT is responsible for the deadlocks, it blocks one UI thread on another, which is not safe because they lock the same native resources.|
Our version that removes those deadlocks and integrates the abandoned Albireo improvements has its own issues. Java's own SwingNode class is a big improvement over SWT/AWT: it has the right level of access to Swings internals to be able to get things right without (as?) weird hacks, and they made the right assumption, that all communication between the two UI threads must be asynchronous, unlike SWT/AWT.
Of course, one still has to keep in mind that it's a multi-threaded UI, and be sure to never block from one UI thread on the other (which even requires odd things like never checking whether you're on the AWT thread from the SWT thread), but with the right thread-switching tools it's possible to embed Swing in SWT via FX.
So the change was that org.eclipse.fx.javafx is replaced by org.eclipse.fx.osgi? Thanks!
[Updated on: Fri, 21 July 2017 18:44]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.01592 seconds