Fullscreen on external Screen/Projector | jit.world ignores windowposition attribute

Nodanoma's icon

Hey all,
preparing for an installation, I need to move the jit.world window to a connected projector/screen and enter fullscreen on it. I've never encountered this problem, however, it can be reproduced in a simple setup: Upon entering fullscreen, the rendering window switches back to position 0 0 (i.e. the main screen jit.world is placed in) and toggles fullscreen there — which is probably not intended and surely not useful. Does anyone have a clue as to what I must flag/set to get this working as expected?

Addition: It seems any initial @windowposition attribute away from main screen is ignored by jit.world, i.e., when setting only the windowposition attribute outside of main screen, it appears at its default position… bug?

Thanks mucho!

wndow moves back to main screen, then toggles fullscreen there (not intended)

Max Patch
Copy patch and select New From Clipboard in Max.

Rob Ramirez's icon

platform and OS version? if macOS is "Displays have separate spaces enabled" or not? assuming latest Max version...

[edit] does disabling @floating make it work as expected?

Nodanoma's icon

Thanks Rob!
indeed, I'm on macOS and »separate spaces« were enabled — unflagging this setting solved the issue!
Sidenote: If the windowposition is vertically at '0' the fullscreen is cropped and doesn't cover entire screen, then, when exiting fullscreen it has no title bar. Changing the initial pos solved this too.

Changing the 'floating' flag initially had no effect (perhaps obviously now), with separate spaces disabled there is no problem.

Cheers!

Rob Ramirez's icon

ok thanks. well the bug is still there but you've simply hidden it away. there is different behavior on different versions of mac depending on that display setting (and other window attributes), so getting all this correct across the board is proving difficult. and in fact i've received another report about breakage when that setting is disabled (which seems the opposite of what you're reporting :facepalm:). we will continue to investigate.

Nodanoma's icon

thanks for the explanation. Perhaps I'll run into more problems once the patch is transported to Windows, which will be the case..