Ben Ward

A 3 pixel gripe about Parallels

. Updated: .

I love Parallels. It lets me work as a .NET developer and still use superior MAC OSX tools for everything that isn’t Visual Studio. There’s not really much to it; a window to pick your Virtual Machine and then a window to display your Virtual Machine. Which is why it annoys me all the more that it doesn’t really slip into the Mac look and feel.

There are a few things I’d like enhanced: More keyboard shortcuts for launching/pausing VMs, the ability to override keyboard shortcuts (so that + will work even when Windows has focus, for example). But though those would be very functional and useful enhancements, my biggest grip is mostly aesthetic.

Look closely at the edge of the Parallels window.

On the Mac, windows don’t have borders. The edges are instead highlighted by the subtle shadow effect on each window. Parallels, for a reason I don’t quite understand, includes 2 pixels of white margin and a 1 pixel black border around the VM workspace. Frankly, it looks yucky. It also proves a pain when trying to set an optimal resolution for the VM. Rather than run fullscreen I prefer to run in a custom-sized Window (you can set custom screen resolutions before boot in the Virtual Machine options).

On my MacBook Pro, this would ideally be 1440x800 pixels (allowing space for the Parallels title bar, OSX menu bar and my Dock). Unfortunately, the margin and border around the VM workspace pads the Window out beyond my screen size, so I must instead use a smaller width. But resolution widths must be multiples of 8, so the smaller width doesn’t fit flush with the screen width.

Yes, I’m being very pedantic. But really, I don’t think it’s unreasonable to ask for a bit of polish on the software I use daily.

Comments

Previously, I hosted responses and commentary from readers directly on this site, but have decided not to any more. All previous comments and pingbacks are included here, but to post further responses, please refer me to a post on your own blog or other network. See instructions and recommendations of ways to do this.

You can file issues or provide corrections: View Source on Github. Contributor credits.