I am showing a frame that has a button. On clicking the button, I am calling gd.setFullScreenWindow(dialog) where dialog is a child of the frame shown and it is modeless. Dialog appears in FullScreen mode. Dialog has a button 'dispose'. On clicking the dispose button, I am calling dialog.dispose(). This actually disposes the dialog shown. When the dialog is disposed, I am surprised to see the parent frame in the full screen mode. Actually, I have never called setFullScreenWindow() for the frame explicitly and calling it for the child dialog pushes the parent frame to full screen mode.

This behavior is noticed on WinXP and not reproducible on Solaris. This bug is reproducible right from Tiger-beta-b26 and not reproducible on B25. Hence this is a regression introduced in b26. This is reproducible with the latest build Tiger-beta2-b47.

I have attached a sample code. Execute it. You would see a frame with a button. Click the button. A dialog would appear in FullScreenMode with a button. Click the button on the dialog. The dialog will get disposed. If you see the parent frame in FullScreen mode, the bug is reproduced.

Here is the platform info:
Platform configuration:

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

Operating System:
Windows XP (version 5.1 Service Pack 1 (Build 2600))

DirectX version: DirectX 8.1 or greater

DirectX display devices:
Device 0:
  Resolution (width x height x depth): 1024 x 768 x 32
  Video memory (Total, Free): 6291 KB, 6291 KB
  Device driver ialmrnt5.dll version 6.13.1.3442

GDI display devices:
Primary: Name = \\.\DISPLAY1, Description = Intel(R) 82845G/GL/GE/PE/GV Graphics Controller