Disable macosx top menu bar on fullscreen -> fixed in 3.1.0/SVN

I would really appreciate such an option.

With the current behaviour the upper screen edge is rather unusable for the VM.

(already asked in the forums recently -- http://forums.virtualbox.org/viewtopic.php?f=8&t=21676)

subscribe

+1

I, too, would greatly appreciate the addition of this feature.

I too would like to echo support for such a feature. It makes it very irritating using a Gnome guest under a Mac OS X host.

However I have not seen the Dock while working in full screen mode with mouse integration enabled? It only seem to occur with the OSX menu bar and the VirtualBox minibar. I can live with the minibar -- just not the Dock and the OSX menu bar!

This behavior is now changed. I disabled the auto showing of the dock and the menu in the next major version of VirtualBox.

Thank you poetzsch!

Glad! Thank you!

Thanks very much!

Added myself as CC.

-Technologov

Alexey, can you confirm that this bug is fixed? The code should already be in 3.1.0 Beta1.

@frank: I am happily using the beta without the top bar on fullscreen :) It was also on the release changelog, did you read it?

Ok, I appreciate your feedback :-) I just wanted to be 100% sure that this is fixed.

I did not face the problem above as I am using a dual-screen setup on my Mac. However, with this new fix, the menu to change to Full screen and Seamless mode is no longer accessible. Meaning I need to use the hotkeys to change the display.

Suggestion: Provide an option to turn on or off the Dock and Menubar display. It is personal preference for the visibility of both of the item.

ARGH !

Add an option please, I understand other needs, but mine is currently ruined :-(

I was fully happy with the top menu bar and dock appearing with the mouse integration disabled.

Most importantly, with the new behavior I've lost the ability to use cmd-H to quickly come back to OSX !

That means the wonderful user experience consisting of: - from OSX to guest: click the icon in the dock - from guest to OSX: press cmd-H is now lost.

Instead, I need to use host-F to come back to OSX but even there, the guest is not hidden anymore :-(

Alternatively some host-? shortcut to hide the VM will be fully satisfying too :-D

@vila:

- Host-H is working as before, for me, both on fullscreen and window mode. - If you need quick access to the bar, you can also maximize window without entering fullscreen. Fullscreen is intended to be used when you don't have to switch between other apps than the guest machine and use full screen resolution.

@gionn: host-H doesn't exist here and cmd-H has stopped working (I tried hard, believe me). I've discovered these issues after an upgrade to OSX 10.6 and vbox 3.1.0, may be that can explain the different behavior. Also, I spend most of my time in the guest, so fullscreen is really what I want.

Two more remarks:

1) cmd-Q has been lost too

2) I've found an acceptable workaround for the lack of cmd-H: 'host' key followed by the expose key gives me a quick way to select my target application in OSX or anything on the dock. To come back to my guest, I can click its icon in the dock like before. The main difference with the previous workaround (involving host-F) is that it avoids the ugly redimensioning of the screen.

\o/

Hope that can help others, yet, host-H and host-Q as aliases to cmd-H and cmd-Q would be really welcome !

Here the same: OSX 10.6 with all updates and 3.1.0, and I am with the default host key (left cmd): any problem at all with every keyboard shortcut you can see on the Guest menu.

Right, I use the right option key, I think that explain it.

ISTM that neither cmd-H nor cmd-Q are bound to the host key, you get them working because you din't redefine the host key, so good for you, they still work because they are by default bound to the cmd key.

So the bug can be viewed as the lack of binding to the host key for H and Q, I let the devs decide :-)

Ok, now that you get it, I think you should probably file a new bug about that.

See #5684 for the CMD+Q & CMD+H problem. See #5636 for the solution of this problem.