UX messed up when switching from monitor

[Christopher-TD]

Somehow all the toolboxes, layer palettes etc have vanished. The trigger was leaving AD2 running when the laptop slept and then unplugging the laptop monitor so the window switched to the internal screen which has a lower resolution.

Nothing I do restores these to somewhere I can interact with them, even when plugged back into the monitor.

Is there a way to reset the UX to a workable state without deleting and reinstalling the app? It is basically useless in this state.

Every time I revert to the laptop the window doesn't resize properly and cannot be resized.

Thanks

Christopher

macOS Sonoma 14.1.2

MacBook Pro 14" M3 Max 

[Christopher-TD]

I did manage to restore some of the UI by selecting Collapse All in Layers Panel, which didn't make a whole lot of sense, but it did work. 

The issues when switching screen resolutions remain though. 

[walt.farrell]

Try Window > Zoom from the menu.

From the FAQ:

 

[Christopher-TD]

Thanks. That will be useful to know until the issue is resolved. 

[debraspicher]

Use Windows key + Shift + arrow keys left/right to move your stuff back to your other monitor.

Oops, sorry. Forget this section is Mac OS too 🤕

Do check Mac OS shortcuts though, because very likely there's a shortcut where you can move/snap your windows to other screens or back to your main... when I end up with windows being cut off, this is what I do to get them to a state so I can put them back where I want them...

[Christopher-TD]

Thanks - will look out for this. In my case the two screens aren't ever active at the same time, but some kind of keystroke to trigger it to reorganise itself will be handy

[v_kyr]

On 12/10/2023 at 8:07 AM, Christopher-TD said:

... Every time I revert to the laptop the window doesn't resize properly and cannot be resized. ...

Hmm, it should be usually possible to do that from outside of ADe via some Apple scripting and the like. - For example in order to get the laptop monitor resolution (if only that one is active and nothing else as external monitors is connected), one can perform in a command shell (macOS Terminal.app, or iTerm.app, etc.) the command ...

Quote

> system_profiler SPDisplaysDataType | grep Resolution
          Resolution: 1920 x 1200

... which will give back then the laptop monitor resolution. When a bunch of monitors is actively used (aka also external connected ones), then the resolutions of all are listed instead.

Further one can also size application windows via AppleScript. - Here's an example for "Safari"...

Quote

tell application "Safari"
    set bounds of front window to {100, 30, 900, 700}
end tell

... where ...

Quote

set bounds of front window to {x, y, width, heigh}   // in pixels

So by using in Automator an Apple script like this one ...

Quote

tell application "Affinity Designer"
    set bounds of front window to {50, 30, 900, 700}
end tell
 

... or ...

Quote

tell application "Affinity Designer"
    set the bounds of window 1 to {50, 30, 900, 700}
    activate
end tell

... should then resize the ADe app window accordingly to ...

• x = 50
• y = 30
• width = 900
• height = 700

NOTE: ...this is just out of my memory here. Meaning I didn't actually tested the above yet for ADe/APub/APh.

 

Another way, for macOS >= Monterey users, might be to use the macOS Shortcuts.app as described here ...

• The Easiest Way to Resize All Windows on Your Mac Simultaneously to the Same Dimensions

... as far as an Affinity apps main window can react and thus be be controlled that way (...the same would apply here to support by Apple Scripting at all).

[Affinity Info Bot]

The issue "[macOS] App Window Disappears after disconnecting and re-connecting an external monitor between app sessions" (REF: AF-417) has been fixed by the developers in internal build "2.4.0.2211".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.