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

FULLSCREEN: FullScreen/...Blitting_SimpleFullScreenAssertion fails in Alt+Tab

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: P4 P4
    • 5.0
    • 1.4.1_02, 1.4.2
    • client-libs
    • 2d
    • tiger
    • x86
    • windows_2000
    • Verified

      Filed By : J2SE-SQA
      JDK : JDK1.4.1_02fcs (b6), JDK1.4.2 b18
      Platform[s] : windows 2000 pro SP3
      switch/Mode : -cleint
      test harness : tonga 1.2 (52)
      testbase : /net/cady/export/dtf/unified/knight-ws/suites/awt/testbase (was /net/sqesvr/export/st2/suites/mantis/awt)
      Falling test[s]:
      AWT_Mantis_WS/src/FullScreen/Blitting_SimpleFullScreen/Interactive/src/BltSimpleFullScreenAssertion

      The instruction says "ALT+TAB" can shift between FullScreen and other applications. When I do the Alt-Tab at the first time, the FS get minized. I do the Alt-Tab again, the FL comes back but I still can see the Windows Start menu in the bottom of the whole window.


      Attached BltSimpleFullScreenAssertion.tar.Z contains all required files to run the test:
      BltSimpleFullScreenAssertion.cfg* Pass_Fail_Inst.txt*
      BltSimpleFullScreenAssertion.class* VERSION*
      BltSimpleFullScreenAssertion.err* readme.txt*
      BltSimpleFullScreenAssertion.java* script.ksh*
      BltSimpleFullScreenAssertion.out*
      BltSimpleFullScreenAssertion.tlog*

      How to reproduce:
      ==================
      1. Run the tlog (Modify tlog for correct path)
      2. Click OK in instruction window to start the test.
      3. Use Alt-Tab to minize the FullScreen. Use Alt-Tab again. You'll see the Windows start menu bar at the buttom of whole window.


      Failed Machine config:
      =====================
      1.
      machine name: qavectra
      Display Propertites setting Colors: True Color (32-bit)

      output of /net/jano/export/disk06/java2d/win32utilities/PlatformInfo/Release/PlatformInfo.exe
      Platform configuration:

      CPU:
      Intel 32bit
      Single Processor
      Processor Speed: 498 MHz

      Operating System:
      Windows 2000 (version 5.0 Service Pack 3 (Build 2195))

      DirectX version: DirectX 7

      DirectX display devices:
      Device 0:
        Resolution (width x height x depth): 1024 x 768 x 32
        Device driver atidrab.dll version 5.0.2180.1

      GDI display devices:
      Primary: Name = \\.\DISPLAY1, Description = ATI Technologies Inc. 3D RAGE PRO AGP 2X

      2.
      machine name: maia
      Display Propertites setting Colors: 256, True Color (32-bit)

      CPU:
      Intel 32bit
      Number of Processors: 2
      Processor Speed: 797 MHz

      Operating System:
      Windows 2000 (version 5.0 Service Pack 3 (Build 2195))

      DirectX version: DirectX 7

      DirectX display devices:
      Device 0:
        Resolution (width x height x depth): 1024 x 768 x 32
        Device driver G400D.dll version 5.12.1.1120

      GDI display devices:
      Primary: Name = \\.\DISPLAY1, Description = Matrox Millennium G450 Dual Head - English


      ###@###.### 2003-03-24
      =================================================

      ###@###.### 2003-09-11
      ls
      ./ SCCS/
      ../ SimpleFullscreenTest$1.class
      MyWindow.class SimpleFullscreenTest.class
      MyWindow.java SimpleFullscreenTest.java

      Also, modified the testbase path to /net/cady/export/dtf/unified/knight-ws/suites/awt/testbase

      ------------------------------------

      Note that the attached tar file for SimpleFullscreenTest does not work because the absolute pathnames (/net/cady/...) are embedded in the tarfile. I did get the SimpleFullscreenTest and MyWindow files, but had to search around a bit: they are
      found in the AWT_Mantis_WS directory mentioned above, in the subdirectory
      src/FullScreen/Blitting_SimpleFullScreen/Lib/Classes

      ###@###.### 2003-09-17

      To simplify test, I wrote a very simple app that mimics the behavior of the test above, called SimpleFSWindow, attached to this bug report. This test creates a Frame, then creates a Window owned by that Frame, then goes into fullscreen mode on that Window. When it works, you should be able to alt-tab in and out of that application and see: an all-white screen when in the fullscreen app, and a normal desktop when the fs app is minimized. Buggy behavior shows, for example, the start menu over the white fs app when running in the app itself and possibly never getting back to a normal desktop when alt-tabbed out of the fs app.

      ###@###.### 2003-09-18

            chaasesunw Chet Haase (Inactive)
            schien Suchen Chien (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: