Yep, I will do. 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.
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. Anyway, that is a totally different issue. On 21 July 2011 18:42, Greg Brown <gk_br...@verizon.net> wrote: >> I'll rephrase to try to better describe what I had observed. >> - Pivot app in OS window 'A' has a focused TextInput. >> - OS window 'A' is decorated as active by the OS >> - The same Pivot app has a 2nd Display in OS window 'B' >> - User clicks on the chrome of OS window 'B' to activate window 'B' >> - The TextInput retains focus, meaning it will receive key stroke >> events, even though it is not a descendant of OS window 'B'. > > This does sound like a legitimate bug. If you are able to reproduce it, > definitely log it in JIRA. > > G > >
