flamingo
  1. flamingo
  2. FLAMINGO-43

Ribbon application menu does not repaint properly if sun.awt.noerasebackground is set to true

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 4.0
    • Fix Version/s: milestone 1
    • Component/s: ribbon
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      43

      Description

      If the sun.awt.noerasebackground attribute is set to true, the ribbon
      application menu will not repaint correctly the second time it is displayed.
      Comes up okay the first time you click it, but does not appear the second time
      it is selected. I'll attach a screenshot shortly showing the problem. The
      screenshot shows the problem under Substance Raven, but I've verified the
      behavior is the same under Metal.

      The workaround is to not set this system property. We were formerly setting it
      as legacy from pre-1.6 days where it was very helpful with gray rectangle issue.
      Legacy applications upgrading to the ribbon may be setting this attribute, or
      for applications that need to run on earlier platforms (i.e. 1.5, since I don't
      think Flamingo officially supports before that). Given our paying customers all
      have deployments upgraded to Java 6, I'm going to pull the property for our
      applications.

      As an aside, they need to update the OS choices. Windows Vista 64-bit is not in
      the list; JDK 1.6.0_11 was used here as well.

      1. Main.java
        3 kB
        flynnk
      1. issue43.png
        16 kB
      2. screenshot.jpg
        72 kB

        Activity

        Hide
        flynnk added a comment -

        Created an attachment (id=15)
        Ugly screenshot showing the problem

        Show
        flynnk added a comment - Created an attachment (id=15) Ugly screenshot showing the problem
        Hide
        flynnk added a comment -

        Created an attachment (id=16)
        Sample program to reproduce the problem

        Show
        flynnk added a comment - Created an attachment (id=16) Sample program to reproduce the problem
        Hide
        kirillcool added a comment -

        Created an attachment (id=17)
        Screenshot on my machine

        Show
        kirillcool added a comment - Created an attachment (id=17) Screenshot on my machine
        Hide
        kirillcool added a comment -

        Attached screenshot of this test app on my machine. Windows Vista, JDK 6u10, no
        hardware acceleration (embedded Intel graphics card).

        What is your configuration? Can you try to disable the D3D acceleration with
        -Dsun.java2d.d3d=false?

        Thanks
        Kirill

        Show
        kirillcool added a comment - Attached screenshot of this test app on my machine. Windows Vista, JDK 6u10, no hardware acceleration (embedded Intel graphics card). What is your configuration? Can you try to disable the D3D acceleration with -Dsun.java2d.d3d=false? Thanks Kirill
        Hide
        flynnk added a comment -

        That's it. Turning off d3d with the argument fixes the problem also. I'm
        running on dual NVidia cards, so that's probably part of it. This is probably
        going to be a pain to fix if you cannot reproduce it locally.

        Show
        flynnk added a comment - That's it. Turning off d3d with the argument fixes the problem also. I'm running on dual NVidia cards, so that's probably part of it. This is probably going to be a pain to fix if you cannot reproduce it locally.

          People

          • Assignee:
            kirillcool
            Reporter:
            flynnk
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: