Hi Sandro. Welcome back! I just run KitchenSink as usual (built and packaged from the 2.0 tag in SVN), and then press CTRL+SHIFT+F to switch between normal and fullscreen modes.
It appears to be fixable by changing the order in which the java.awt.Frames are made visible & hidden in org.apache.pivot.wtk.DesktopApplicationContext.setFullScreen(boolean) I was working on a custom DesktopApplicationContext when I saw this, and have been able to fix it in my version (still on MS Windows XP 64). I haven't had a chance yet to see how it works on any other OS, but plan to check Ubuntu, XP32, Win7 32 & 64. Chris On 25 July 2011 00:31, Sandro Martini <sandro.mart...@gmail.com> wrote: > Hi all, > >> I have just seen another funny thing that I can only reproduce on >> Windows XP 64 (with 32 & 64 bit JREs) so far, and not on Ubuntu 10.10 >> or Windows XP 32. So maybe XP64 is a bit odd, which wouldn't surprise >> me as it wasn't widely used. > I can try on Windows 7 at 64 bit ... > >> Putting a Pivot 2.0 desktop app (such as KitchenSink) into fullscreen >> mode and then back to windowed mode leaves 2 taskbar buttons in the >> Windows Taskbar (regardless of how many times the mode changes). 1.4, >> 1.5, 1.5.1 & 1.5.2 and before seem to work fine, and only leave 1 >> taskbar button when returning from fullscreen mode. > Chris, what exactly should I do (use some keystrokes or some change to > the code) to test the behavior ? > > Bye >
