Keyboard Shortcuts in Unity

[PeteGingaNinja]

OK, I love Unity, It's much better than Coherence in Parallels, but, I also like the Start bar, so when my guests are using my Mac than can still feel at home if they are Windows users rather than Mac users.

So I have shown the Taskbar in Unity by editing the tools.conf file, and there it is, great!

But when I switch to Unity mode, I cannot use the Apple (Windows) Key or any of the shortcuts, especially my favourite, Start+R!

I know that there is some remapping being done in Unity mode and I was wondering how I can stop it!

[vinayv]

Yes, currently the Apple-Key is remapped to the Ctrl Key in Unity mode. This is for the making normal mac shortcuts work like one would expect in Windows. Currently there is no way to turn this off.

I'll ask Pat to toss it on our list of things to look at.

[PeteGingaNinja]

OK, this applies now to Beta 1 of Fusion 2.0!

I'm running WIndows XP 32-bit and I've turned off Mac Mouse Shortcuts, but left on Mac Keyboard shortcuts.

In Vista, I can happily Control Left Click no problems and press the Start Keyboard Key and use Start + R, no problems.

But in Windows XP 32-bit I can't no matter what combination of options I use / which Tools version is installed.

I need to be able to Control Left Click, and use my favourite Start + R shortcut! what can I do!?

Pete

[PeteGingaNinja]

Further more, I've recently installed OneNote and that requires the Start Key as well! Start + N to open a New Note and Start + Shift + N to open up OneNote.

I also need the Start key as I develop a program that runs in Full screen and whenever I need to access another program, I normally just press the Start key and there's my Taskbar, but now I can't!

I run Fusion in Unity mode all the time and want/need this key! Please unmap it from Control, as I don't want to run it in Full Screen Mode.

Just to let you know, Parallels works fine with this key in it's Coherence mode, but I don't want to switch back to Parallels just because of the Start key!

[sailesh_a · Accepted solution]

This issue has been fixed internally. Thanks for the feedback.