rxhanson / RectanglePro-Community

Bug reports and discussion for the Rectangle Pro app
https://rectangleapp.com/pro
98 stars 1 forks source link

Cycle through displays is not using the full screen width #272

Open globetro opened 1 year ago

globetro commented 1 year ago

I'm using an ultrawide monitor and my laptop screen

When I use the "maximize" shortcut to cycle a screen from my laptop screen to the ultrawide screen, it doesn't fill the full screen on the ultrawide monitor and instead maximizes it about 75%, leaving 25% of the screen on the right still open.

This only happens when I cycle it up to the wider monitor. When I cycle it back down to my laptop screen, it fills it 100% no problem. Also, if I have a screen already on the ultrawide monitor and I use Rectangle Pro's "maximize" shortcut, it works fine and fills the screen 100%. But if I press it again to cycle it to my laptop (it's still fine, 100% fills laptop screen), and then cycle it back up to the widescreen, it's once again only expanding 75% horizontally. And in all cases, it expands vertically 100% without issue.

This seems to be a new bug as I haven't seen this issue until recently.

rxhanson commented 1 year ago

Thanks for reporting. This issue was first reported when Ventura was released, and is due to something that changed on the macOS side. It seems to only affect certain displays, and the workarounds I've tried haven't panned out. I'll update here if I can figure out a workaround that works.

lgarron commented 1 year ago

I seem to have the same issue now.

I have a 5K monitor, which is 2560@2x resolution across. Rectangle Pro used to resize to the full width, and it now resizes to 2160@2x across (leaving the right-most 400px@2x unused):

Screenshot 2023-06-20 at 12 40 09
lgarron commented 1 year ago

Aha! From https://github.com/rxhanson/Rectangle/issues/917 I learned that this is an issue with pin mode. I tried using pin mode to keep a window on top, but it also seems to have undesirable side effects.

rxhanson commented 1 year ago

@lgarron thanks for your update! I'll add in a backlog item for handling this scenario in Pin mode.

lgarron commented 1 year ago

@lgarron thanks for your update! I'll add in a backlog item for handling this scenario in Pin mode.

Thanks!

I'm able to solve this by setting the pinned application width to 0, but it would be nice for the "keep a window on top" feature to be separately available from the right gutter sizing. (EDIT: actually, looks like pin mode no longer works keeps the window on top you resize the window after revoking? I'm almost certain that worked when I first tried it, but it seems I was testing incorrectly.)

(I'm using it to keep Microsoft Teams on top, which — despite being overzealous about getting in your face in other ways — weirdly does not have a built-in feature for this like Zoom does.)

imyelmo commented 11 months ago

I'm having the same problem sometimes, "sometimes" means that I cannot exactly define the trigger for the misbehaviour. The problem seems solved after disabling pin mode, which seems appealing in ultrawide monitors (one of my usecases). @rxhanson, let me know if you need further information but it seems that you know something related with the issue.

nille commented 11 months ago

I'm also having the same issue. For me it is on just one of my two external display (both of the same make/model) and happens about 90% of the time. On rare occasions it till actually maximize as should. I have pin mode disabled and have also tried toggling it on/off with no effect. Also tried setting the pinned application width to 0 as @lgarron mentioned but with no effect. I use two external displays (one horizontal and one vertical) plus the built-in display on my Macbook Pro. I don't recall ever having this issue before or with the "regular" Rectangle version.

Apple M1 Pro, 32 GB
macOS V13.6 (22G120)
Rectangle Pro v3.0.13 (154)
rxhanson commented 11 months ago

@imyelmo I actually put in some changes in a previous release that apparently didn't fix pin mode. Let me go back through it again and see what I can do.

@nille your issue does not seem to be related. Can you provide logs? Hold the option key in the menu bar menu and select view logging. It's also preferable to open a new issue since yours is different, if you don't mind.