Hello there, Ive been seens this one since a while…
when you save a patch with a windows in full screen its not possible to get out of the fullscreen mode…
1- take any patch exemple with a stride windows
2- presse alt-F4 to fullscreen on a second screen
3- save the patch and close it
4- reopen the patch
5- the windows is still on fullscreen but the alt F4 doesnt do anything…
I have delete the scene window and ctrl z to get the the windows again
It doesnt happen with skia renderer… (but this one doesnt save the fullscreen state)…
When you reopen the patch the window is most likely not in fullscreen but windowed (kind of) borderless*, the window having the same size as the screen. When using F4 you are now switching between windowed borderless and fullscreen and you will see almost no difference. When hovering the border that is adjacent the main screen with your mouse it should turn into a resize cursor. Resizing slightly will get the title bar back.
ok thanks I see,
But Is this a normal behaviour? Seems confusing to me…
Specially if you have several output and projector… and you just want to bring the window back to your main screen lets say…
I would prefer to have a more clear distinction between state…
Now with the last preview, saving a patch with the fullscreen on, I cant even take back the side of the screen to get out of the fullscreen… its stay stuck… oly way…removing the node
Weird, I just downloaded latest preview 7.1-0072 and if I save a stride patch with a fullscreen window it opens as normal size window where it was before pressing Alt-Enter.
But either way, windowing, or managing where windows go during startup is basically always a thing that you want to control.
You can just specify your own location and size on Create:
Hm, 7.1-0072 made it so that it no longer stores the bounds when the window is fullscreen as that was not correct at all. On a restart the window would open with those bounds in non-fullscreen, leading to a border around the window which in turn could prevent the hardware independent flip from working correctly. Therefor step one was to remove that behaviour entirely. For now use the SetFullscreen and/or SetWindowState nodes to control your window on startup. We’ll most likely do another iteration on that topic.
They are running after the window was created, but we would need to set the initialization parameters, so that the window doesn’t flash around on startup.
Indeed it working again in 0072…. the trouble I had was in the 0069
and yes I use the Setfullscreen … but question about that while Im here… Does the input toggle fullscreen behave how it sould? There is a togedge so the switch between the two state happend only when the toggle is true…
Toggle True = fullscreen
Toggle false = nothing
Toggle true again = windowed
edit: Ho, Just seeing this, when its on fullscreen… now its always on top of anything else… (I didnt select the option on the top bar) is this normal?