https://javafx-jira.kenai.com/browse/RT-40437
On 6-4-2015 16:25, David Grieve wrote:
You should file an issue in jira for this.
On 4/6/15 3:31 AM, Tom Eugelink wrote:
On 6-4-2015 00:58, David Grieve wrote:
On 4/5/15 3:56 AM, Tom Eugelink wrote:
I have another interesting behavior involvin
You should file an issue in jira for this.
On 4/6/15 3:31 AM, Tom Eugelink wrote:
On 6-4-2015 00:58, David Grieve wrote:
On 4/5/15 3:56 AM, Tom Eugelink wrote:
I have another interesting behavior involving CSS. The gauge has a
text representation of the value of the needle, which can be
for
On 6-4-2015 00:58, David Grieve wrote:
On 4/5/15 3:56 AM, Tom Eugelink wrote:
I have another interesting behavior involving CSS. The gauge has a text
representation of the value of the needle, which can be formatted using
DecimalFormat. The format string can be set with a styleable property.
On 4/5/15 3:56 AM, Tom Eugelink wrote:
I have another interesting behavior involving CSS. The gauge has a
text representation of the value of the needle, which can be formatted
using DecimalFormat. The format string can be set with a styleable
property.
In the example this property is set,
I have another interesting behavior involving CSS. The gauge has a text
representation of the value of the needle, which can be formatted using
DecimalFormat. The format string can be set with a styleable property.
In the example this property is set, via setStyle(), to something with a unit po
After loads of trail and error I pinned it down to the fact that scaling of the
node in question was not taking into account when positioning it; it is
centered and I use its width to do that, but it was the width-before-scaling.
So it was a miracle it was in the right place at all. What really
How exactly can you use pseudo-class state for this sort of change?
I have a similar requirement in my own app. It always did feel a little
'heavy' when I added and removed style-classes, but it still seemed like
the best way to trigger visual changes on my nodes.
Though I guess one benefit is th
When you add or remove style-classes, CSS for the node (and all its
children) is totally re-calculated. This means that cached data for that
node is tossed out and the node is styled from scratch, as if it were
just added to the scene-graph.
You are much better off using pseudo-class state for
One addition: the move happens if, for example, "segment0-active" is added to
the skinnable. Even if that class is empty or even not defined in the CSS.
Tom
On 3-4-2015 19:48, Tom Eugelink wrote:
I'm pushing the envelope a bit -I think- concerning the use of CSS. I have setup a control (gauge)
