Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8104949 Poor Performance for Typical Apps
  3. JDK-8105594

Computing pivot point for every FXNode even if not necessary

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Icon: P2 P2
    • fx1.2
    • None
    • javafx
    • None

      Major performance problem for bond demo and also makes it such that changes to the scene creates an enormous number of bounds calculations not otherwise needed. The problem is that in order to compute the pivot point (center of default layoutBounds), we need to recompute a transform every time the bounds, effect, opacity, clip, cache, or transforms[] change. This means another set of notifications and further bounds changes. This one fix alone made a dramatic improvement in the transition performance of bond demo.

      Its a one-liner. Simply need to only do the pivot calculation when rotate, scaleX, or scaleY are in use.

            rbair Richard Bair (Inactive)
            rbair Richard Bair (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported: