One thought is maybe the border is still there in the canonical full screen version, but it's placed outside of the monitor. It's not clear why we have to toggle WS_OVERLAPPEDWINDOW in that case, but I figured I'd test this by shrinking the rectangle in by 100 on each side.
-
Show this thread
-
Result? There was no border when I used the canonical version with the size shrunken in! Then doing the opposite experiment I took out the SetWindowLong, and the border came back. If I used SetWindowLong to add in WS_OVERLAPPEDWINDOW I also got the window border.
1 reply 0 retweets 0 likesShow this thread -
If I leave off the SetWindowPos after doing the SetWindowLong, it also breaks but in ways I don't fully understand yet. It's as if nothing can render to the window at all at that point.
1 reply 0 retweets 0 likesShow this thread -
If you want a window without a border the only way to do it is to set a style without WS_OVERLAPPEDWINDOW via the SetWindowLong call and then to call SetWindowPos explicitly. Neither component alone works.
1 reply 0 retweets 0 likesShow this thread -
Why isn't it just a matter of setting the right style and position? Why does the same style/position information from two different methods work this differently? I have no idea, that just seems to be the way things are.
1 reply 0 retweets 4 likesShow this thread -
Replying to @AllenWebster4th
Raymond unhelpfully did not actually explain anything about why CreateWindow wouldn't work directly when he laid out the canonical solution you describe :(https://devblogs.microsoft.com/oldnewthing/20100412-00/?p=14353 …
1 reply 0 retweets 2 likes -
Replying to @cmuratori @AllenWebster4th
It does, however, include the ominous message about the taskbar "recognizing" that a window is going fullscreen and "geting out of the way". That may be a bit of a soft-signal that hey, there's a ton of special-case crap in the guts, and you have to poke it right :/
2 replies 0 retweets 1 like -
Replying to @cmuratori
Usually looking into something feels like it pays off, you're better off now. This time all it feels like is "I didn't want to know this."
1 reply 0 retweets 3 likes -
Replying to @AllenWebster4th
Surely your DPI quest felt similar? You've been in this particular sausage factory before. Some things you can't un-see!
1 reply 0 retweets 0 likes -
Replying to @cmuratori
Yeah that was pretty similar. I mean it was full of surprises, and eyebrow raisers, but by the end I didn't feel like I was throwing my hands up and saying "I don't know". I could get the idea behind them, even if they were bad ideas. This one is just going to be spooky forever.
1 reply 0 retweets 1 like
It is part of Microsoft's new "Spooky Forever(R)" initiative.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.