F12 menu appears even if WinUAE is not in focus

[thomas]

If you use Alt-Tab to move to another application's window and then press F12 in that application, WinUAE opens its config window nevertheless. This is even more annoying if you use multiple instances of WinUAE because all instances open their config window when you press F12 once.

Addition: if you press F12 while the GUI is open, it opens immediately again when you close it.

[chiark]

If another window is able to receive focus - eg an explorer window - , the config window in WinUAE doesn't open for me when f12 is pressed after alt-tabbing out. (2.2 and 2.3b10, WinXP SP3, both windowed and fullscreen)

If there is no other window to accept focus (eg if WinUAE is the only window), then WinUAE still has focus... Even though the title bar text changes.

Before Toni jumps on you, any more info on your setup?

[thomas]

Different PCs, different Windows versions, different WinUAE configs. No specific setup.

[chiark]

hmm, that's odd. I can't replicate it - I've tried on my win7 machine too. (Then again, I couldn't replicate the window sizing bug that Toni said was known, so I'm no good at this testing lark! )

[Toni Wilen]

I can't duplicate. ALT-TAB and then F12 = GUI does not open.

[thomas]

Seems it does no longer happen in 2.3. The PCs I tested had 2.2 running.

However, what did not change and what I only recognised during these tests is that a config with both native and RTG set to windowed, after booting up and Workbench switched to RTG, the mouse pointer is trapped at the left edge of the window. It can only be moved up and down and only a few pixels to the right. Only after F12 and cancel it can be moved over the entire Workbench screen. Logs attached.

[Toni Wilen]

Originally Posted by thomas

Seems it does no longer happen in 2.3. The PCs I tested had 2.2 running.

beta 1: - rawkeyboard hardcoded F12 check ignored focus

However, what did not change and what I only recognised during these tests is that a config with both native and RTG set to windowed, after booting up and Workbench switched to RTG, the mouse pointer is trapped at the left edge of the window. It can only be moved up and down and only a few pixels to the right. Only after F12 and cancel it can be moved over the entire Workbench screen. Logs attached.

Never seen this. Are you 100% sure this also happened in older versions?

[andreas]

Originally Posted by thomas

...set to windowed, after booting up and Workbench switched to RTG, the mouse pointer is trapped at the left edge of the window. It can only be moved up and down and only a few pixels to the right

In windowed mode, if you do NOT press F12+Cancel to stop the mouse from being "encaged", but instead simply ALT-TAB to another application and then back to WinUAE window, can the mouse move "freely" across the screen afterwards or is it still trapped in its tiny area?

[thomas]

Originally Posted by Toni Wilen

Never seen this. Are you 100% sure this also happened in older versions?

I just replaced the existing winuae.exe with the latest beta and I am not sure which version was there before. But the version before had the F12 problem and if you say that beta 1 fixed that one, it must have been one before B1 because it had the F12 problem.

However, I am not so much interested in fixing this. I usually don't use this combination, I only set it in the config for testing the F12 problem.

Originally Posted by andreas

In windowed mode, if you do NOT press F12+Cancel to stop the mouse from being "encaged", but instead simply ALT-TAB to another application and then back to WinUAE window, can the mouse move "freely" across the screen afterwards or is it still trapped in its tiny area?

Alt-Tab and back rescues the mouse from its trap, too.

[andreas]

Alt-Tab and back rescues the mouse from its trap, too.

Thanks for the answer ... go figure, identical behavior here, too.
Maybe just this characteristic might help Toni to get another step forward in finding the problem's origin.