Spectacle: Unable to move applications between displays

Created on 3 May 2016  路  12Comments  路  Source: eczarny/spectacle

I have a dual display setup for my workstation, with the dock at the left hand side of my left display.
When trying to move (using Control+Option+Command+left arrow) a window that is maximized on the right display (the one that doesn't have the dock) to the left display, it snaps back to the right display.

If I manually resize the window to account for the space taken by the dock, I am able to move it.

Most helpful comment

It seems to me, that, whenever the window is bigger than the resolution of the other display, it cannot be moved to that display using spectacle, if I make it smaller, it works.

All 12 comments

+1 This started happening after upgrading to v1.0.5 (590) this morning.

Same thing here, I tried quitting and relaunching the app, and changing the shortcuts but it doesn't work anymore. Same version -> 1.0.5.

Same thing here.

It seems to me, that, whenever the window is bigger than the resolution of the other display, it cannot be moved to that display using spectacle, if I make it smaller, it works.

Not exactly if the window is bigger that the target display, but if the window-width is bigger than the target display, then the window is not movable.
Shortening the window width makes it movable to the smaller display.

same for me, after latest update is got broken

Yup, I confirm it on my side as well: if the window is bigger than target display, it snaps back.

I was just able to reproduce the issue. Unfortunately I don't have multiple displays at home so I need to work on this after hours at the office. It may take me a bit of time to track down a fix but I'm confident I'll have something ready this week.

Can folks see if this build helps at all?

https://s3.amazonaws.com/spectacle/downloads/Spectacle+1.0.6b.zip

@eczarny That build seems to work properly when moving bigger window to smaller display. Thanks!

@eczarny Checked your latest build and it fixes this thread's issue. Many thanks!

if it's any help, the problem was introduced between 1.0.4 and 1.0.5 - I reverted to 1.0.4 and this works fine

Was this page helpful?
0 / 5 - 0 ratings