Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-4118179

Non-optimized drawing shouldn't be *totally* non-optimized

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Fixed
    • Icon: P4 P4
    • 1.2.2
    • 1.2.0
    • client-libs
    • 1.2.2
    • sparc
    • solaris_2.5.1

      This is a followup to bug 4110854.

      The solution proposed by Jeff is to have isOptimizedDrawingEnabled return false. This forces each component intersecting the paint region to be drawn, however it *still* completely ignores the value returned by isOpaque().

      Thsi causes a problem because if any component that intersects the invalid region requires substantial rendering time, the rendering of all the intersecting components suffer.

      I would argue that the top most component should maintain the "One True" invalid rect. When told to repaint it should compile a vector of the components that intersect the dirty region. Once this list is created, it should find the bottom-most component that completely covers the invalid region and, starting with it, work it's way upwards telling each component to repaint.

            svioletsunw Scott Violet (Inactive)
            duke J. Duke
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: