Re: A lot WARING with CSS

2013-12-15 Thread Yennick Trevels
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

Re: A lot WARING with CSS

2013-12-15 Thread Tom Eugelink
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

accessibility

2013-12-15 Thread Michał Zegan
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?

Re: discussion about touch events

2013-12-15 Thread Assaf Yavnai
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

Re: [announce] InhiBeans: mitigate redundant recalculations

2013-12-15 Thread Scott Palmer
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.

Re: [announce] InhiBeans: mitigate redundant recalculations

2013-12-15 Thread John Hendrikx
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

Re: [announce] InhiBeans: mitigate redundant recalculations

2013-12-15 Thread Scott Palmer
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

hg: openjfx/8u-dev/rt: RT-34564: PieChart labels are overlapped by control

2013-12-15 Thread hang . vo
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

Fwd: Re: accessibility

2013-12-15 Thread Michał Zegan
Resending because of wrong recipient: -- Treść oryginalnej wiadomości -- Temat: Re: accessibility Data: Sun, 15 Dec 2013 17:05:55 +0100 Nadawca: Michał Zegan webczat_...@poczta.onet.pl Adresat: Joe McGlynn joe.mcgl...@oracle.com Unless my informations are outdated, I know that at this time java

Re: [announce] InhiBeans: mitigate redundant recalculations

2013-12-15 Thread Tomas Mikula
On Sun, Dec 15, 2013 at 6:39 PM, Scott Palmer swpal...@gmail.com 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