Glad you were able to fix your issue. If you don't need to apply the
effect to the group with the animating content, then it will be able to
be cached, which is where I guess the speedup is coming from.
-- Kevin
On 10/4/2018 1:44 PM, Tom Schindl wrote:
Hi Kevin,
Thank you for the comment
Hi Kevin,
Thank you for the comment so the trick to fix my problems is that I
don't apply the effect on the container but create a 2nd node who has
the same size and is a sibling of my area and apply the effect there?
This looks like it is working ;-)
package fxbugs;
import
Any effect has the potential for slowing down depending on the size if
the node being rendered, since it is done as an image operation on the
entire area (bounding box) covered by the Parent. Have you noticed
whether DropShadow is worse than other effects, say, GaussianBlur? One
other thing to
Yes, I also noticed that DropShadow causes severe performance degradation.
Dirk
> On 4 Oct 2018, at 13:10, Tom Schindl wrote:
>
> Hi,
>
> Why does applying a DropShadow on a large region cause problem when
> animating nodes contained in that region?
>
>> package fxbugs;
>>
>> import
Hi,
Why does applying a DropShadow on a large region cause problem when
animating nodes contained in that region?
> package fxbugs;
>
> import javafx.animation.ScaleTransition;
> import javafx.application.Application;
> import javafx.geometry.Insets;
> import javafx.scene.Node;
> import
