I encountered the same issue when trying to run my demo application on Android
with the JavaFx Android port.
All my background and border styles wouldn't show up when I had any *-radius
styles defined, once I removed those it was working fine. Back then I thought
this was only an issue on Androi
I'm having loads of CSS warnings and one or two class cast exceptions running
the JFXtras samples (have been reporting them for a long while already). But
there they do not seem to have any visual impact.
On 2013-12-15 11:14, Yennick Trevels wrote:
I encountered the same issue when trying to
Hello,
I have the following question:
Does javafx support or plan to support accessibility?
Another question is: if it is planned, then for what release?
Pavel,
I will summarize my answers here, and not inline, I hope I will touch
all your points.
Let me start my answer with a different perspective.
I think that it is correct to try and make mouse oriented application to
work under touch screens, but its not the same as looking how UI should
Interesting idea.
There is a case I have been curious about and wonder what the best
practices are for it. Suppose you have a case when you are changing
multiple different properties that will be used in a single calculation.
You want to deal with a single change to all of them in one go. E.g.
Since you are only allowed to modify properties on the JavaFX thread (in
most cases), I've been using Platform.runLater() to make sure I observe
only complete changes.
Basically I register an InvalidationListener on the properties that are
relevant, and when one gets triggered I set a boolean
Yes, that does the trick, but this basically means you can't use bindings
for such things. I'm wondering if there might be an opportunity for
another enhancement similar to the block() resume() that Tomas has
implemented, but for receiving size of the notification mechanism.
Effectively it would
Changeset: dd01cc258204
Author:jgiles
Date: 2013-12-13 11:59 +1300
URL: http://hg.openjdk.java.net/openjfx/8u-dev/rt/rev/dd01cc258204
RT-34564: PieChart labels are overlapped by control
! modules/controls/src/main/java/javafx/scene/chart/PieChart.java
Resending because of wrong recipient:
-- Treść oryginalnej wiadomości --
Temat: Re: accessibility
Data: Sun, 15 Dec 2013 17:05:55 +0100
Nadawca: Michał Zegan
Adresat: Joe McGlynn
Unless my informations are outdated, I know that at this time java fx 8
does not have any accessibility or accessib
On Sun, Dec 15, 2013 at 6:39 PM, Scott Palmer wrote:
> Interesting idea.
>
> There is a case I have been curious about and wonder what the best practices
> are for it. Suppose you have a case when you are changing multiple
> different properties that will be used in a single calculation. You wan
Good stuff! This is the sort of thing that might make a good contribution
to extend the standard Bindings class.
Scott
On Sun, Dec 15, 2013 at 5:49 PM, Tomas Mikula wrote:
> On Sun, Dec 15, 2013 at 6:39 PM, Scott Palmer wrote:
> > Interesting idea.
> >
> > There is a case I have been curious
This is of concern to me as I have tried to maintain backward compatibility. It
would be helpful if you would file a bug on this and include your .css file, if
possible.
On Dec 14, 2013, at 3:25 PM, Francisco Javier Godino wrote:
> I have an application running perfectly with JAVAFX 2.
>
> I
On Sun, Dec 15, 2013 at 8:30 PM, John Hendrikx wrote:
> Since you are only allowed to modify properties on the JavaFX thread (in
> most cases), I've been using Platform.runLater() to make sure I observe only
> complete changes.
>
> Basically I register an InvalidationListener on the properties tha
On Mon, Dec 16, 2013 at 1:07 AM, Scott Palmer wrote:
> Interesting, no worse than John's pattern though.
> I thought of using a try/finally to make sure release was called and that
> naturally lead to thinking of try-with-resources, where the "resource" in
> this case is a binding of some sort (or
I understand what you are trying to do. I was wondering if a more coarse
grained approach would be preferable, so a central registration of whether or
not to postpone change events.
So:
Central.postponeAllChangeEvents()
Central.resumeAllChangeEvents()
Or maybe both:
p.postponeChangeEvents()
p
15 matches
Mail list logo
