ID:2161977
 
BYOND Version:510
Operating System:Windows 7 Pro 64-bit
Web Browser:Chrome 53.0.2785.101
Applies to:Dream Seeker
Status: Open

Issue hasn't been assigned a status value.
When you drag the window to the top or bottom of the screen, the Skin's Resize Command doesn't get called... I use it to set the view to the size of the window, and since it doens't get called, I'm left with this: http://prntscr.com/cwccjn
to be clear here, the user is talking about the windows 7 and higher gesture that allows you to maximize by dragging the window to the top or resize to fill vertical space by dragging the vertical resize handle all the way to the top or bottom of the screen
In this case, its windows not notifying byond the resize happened, because byond also doesn't save these coords for when the window closes and re-opens.
Also if you have the game window maximized and drag the top bar down the window becomes smaller and also resize isn't triggered.
In response to MrStonedOne
Are you saying that it can't be fixed?
It's simply difficult to fix. Ideally I'd like to know what message Windows 7+ sends when it does the resize. There has to be one.
In response to Lummox JR
Any way I can help with that?
In response to NSBR
Doubtful, but you're welcome to try. The last few times I tried, the question was Google-proof. If you can find the answer, hats off to you.
In response to Lummox JR
You'll get a WM_WINDOWPOSCHANGED message with the SWP_NOSIZE flag cleared at the end of any sizing event. There's no other message that indicates sizing has finished other than WM_EXITSIZEMOVE which indicates the end of a modal moving/sizing loop.

This link might be of help:
http://stackoverflow.com/questions/9786218/ drawing-in-window-while-resizing-leaves-unpainted-border?rq= 1

lummox, i would use a windows message monitor in some sample application to see what messages windows is raising during these things.

spy++ is an included tool in vs2012, and supports that. (start menu, programs, vs2012, tools, spy++)
WM_MOVE/WM_MOVING precludes the window no longer being maximized and as such is a tear-off event if the maximized flag is set.
Any progress on this?

Doing a bit of googling turned up a couple of links that could be of use:

How Electron devs fixed the issue:
https://github.com/electron/electron/pull/2929

WM_SIZE message that they ended up listening for:
https://msdn.microsoft.com/en-us/library/windows/desktop/ ms632646(v=vs.85).aspx
In response to Loganbacca
I'll look into this again. Now that I'm on Windows 10 it should be pretty easy to see this in action.

The problem here is that I'm already listening for WM_SIZE, but it can be called in all sorts of situations that aren't true resizings: like when the window is first made, for instance.
In response to Lummox JR
I wouldn't have a problem with Resize being called when the window is created.
In response to NSBR
Ironically yes, Resize being called when the window is created could also be useful. We currently call our resize code after a client initially connects to align everything correctly.
In response to Loganbacca
Yep, I do the same.
Firing a resize call on every WM_SIZE during window creation would be a bad idea, because the message can be received more than once during that time frame.
In response to Lummox JR
Any updates on this?
Bump
Bump... Please take a look at this again.

Login to reply.