Page 1 of 1

toolbar status grow and waste space

Posted: 13. Oct 2009, 13:42
by Wakou
When working in windows, within an openSuse guest, if I "slide away" the openSuse panel (taskbar) to give me more screen estate, the vbox top and bottom toobar and status bar grow to use up and waste the extra space!
So, Before:
Image


And after.....


Image

Re: toolbar status grow and waste space

Posted: 13. Oct 2009, 14:02
by Sasquatch
How strange. Does it change if you force a refresh of the VBox window, e.g. changing the size of the window or switch to full screen and back? If you have more evidence and you can reproduce it all the time, please report it with as much info as possible in the Bugtracker (separate account needed).

Re: toolbar status grow and waste space

Posted: 13. Oct 2009, 18:52
by Wakou
Sasquatch wrote:How strange. Does it change if you force a refresh of the VBox window, e.g. changing the size of the window or switch to full screen and back?
No Sasquatch, there is no change when toggling Fullscreen etc....
Sasquatch wrote:If you have more evidence and you can reproduce it all the time, please report it with as much info as possible in the Bugtracker (separate account needed).
I will file bug report when I have time, TY

Re: toolbar status grow and waste space

Posted: 13. Oct 2009, 20:08
by Perryg
Instead of hitting the full screen button on Windows, have you tried the VBox host+F toggle to go full screen?
Nothing wasted there.

Re: toolbar status grow and waste space

Posted: 14. Oct 2009, 13:03
by Wakou
Perryg wrote:Instead of hitting the full screen button on Windows, have you tried the VBox host+F toggle to go full screen?
Nothing wasted there.
Indeed not Perry, I am sure that there are various ways I could "workaround" this issue, seamless mode for instance, but the way I use vBox, i am constantly switching between linux and XP, & feel that this is a "mini-bug" within vBox itself, so I thought it worth reporting here.

Re: toolbar status grow and waste space

Posted: 15. Oct 2009, 16:07
by Wakou
bug report #5231 submitted