As can be seen in the issue notes, I do not believe this issue is Not an
issue and really needs to be fixed.
https://javafx-jira.kenai.com/browse/RT-36146
I hope everyone concerned about the quality of font rendering on Windows
with JavaFX looks at this issue and adds their comments.
Felix
Hi Sean,
I've put the Monocle sources directly in my code directories for
testing purposes. Putting it into a separate Jar is possible and I
thought that pre-compiled jars could be provided via Maven.
I didn't do a complete OpenJFX build, because I was only interested in
the Headless component
Steve,
Thank you for that important addition.
Is it true that this, also, is not a special case?
In other words, is this how it works?
- the input queue contains both Events and Runnables (from runLater() and
the first one containing a call to Application.start())
- one item is processed
Hi Neal,
You are correct. The JavaFX Application Thread is the event thread for
JavaFX. It processes input events, pulses, animations, and Runnables
that are submitted via runLater. Other than the special case when a
nested event loop is spun up (e.g., showAndWait()) a new runnable or
event
Setting this up in a repo with instructions for the slow and the lazy :-)
would be really helpful.
Thank you.
-- Sean
On Wed, Nov 5, 2014 at 10:57 AM, Benjamin Gudehus hasteb...@gmail.com
wrote:
Hi Sean,
I've put the Monocle sources directly in my code directories for
testing purposes.
This is extremely good news. I have no problem to drag that library along in
the JFXtras project (project name seems to be a good match for this usage ;-) and release
it to maven - if that is allowed by the JavaFX license.
Tom
On 5-11-2014 16:57, Benjamin Gudehus wrote:
Hi Sean,
I've put
