WinUAE - Amiga Emulator Forum

Using Snowleopard:

Same issue with the menu (calling on with f11). For the rest its working as 7.2.2.

Again, still working fine with COG 8 and linux - must be a Mac
thing -- have you tried installing it into a new/fresh bottle?

I have the same problem and up to now I haven't any clue to solve it. I hope someone to give us a right answer. Thank in advance!

Hi,

I haven't actually tried on the Mac yet, but according to this post the
issue has to do with the Mac keyboard (or likely keyboard mappings)..see;

http://www.codeweavers.com/compatibility/browse/name/?app_id=1713;forum=1;msg=81241

That may not be an option for you however - let me know how if it's not
and I'll spool up winUAE on the Mac and see if there's another solution..

Cheers!

Hi,

The following workaround solves the endless-loop-when-pressing-OK-or-Cancel issue of the popup config menu. I'm using the latest WinUAE under CXG 9.1/Mac in Full Windowed mode.

1. Press the config menu hotkey (F12).
2. Mess around with the config.
3. At this point the config window is in focus. Click on the WinUAE screen outside the config window, so the window loses focus, then press and release F12.
4. Press OK or Cancel and the dialog will disappear as expected.

I suppose the cause of the problem is that WinUAE doesn't receive an F12 key release event after displaying the config dialog, and the workaround forces a release event to be sent "manually", which fixes the infinite loop problem.

Hope this helps.

Janos

Hi Janos,

Thanks for the input!! (no pun intended ;) I've only had a Mac here for  

a month or so (I'm still 'learning the ropes' as it were), but one of the
reasons I got the machine was to be able to specifically test not just linux,
but also Mac usage as well against the same apps I'm advocate for...(and all
else to do with using Crossover on -both- platforms).

I just tested your resolve here, and what you say is indeed correct, and
what I suspected -- the custom keyboard mappings in OSX 'intercept' the F12
(and other) key events, and so winUAE never 'sees' them as it should. What
you describe works a treat, so the effective resolve here is not to use a PC
keyboard, but to understand your operating system of choice better ; thank you
for making me that little bit wiser and sharing your knowledge here!

Cheers!

Hi Don,

You're welcome, I'm glad that I could be of help.
Enjoy your shiny new Mac! :)

Cheers,
Janos