start: Make nCmdShow better match how Windows sets it #17799
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Partial follow up to #17763 (comment) (cc @e4m2)
nCmdShow
is a parameter of WinMain that "Controls how the window is to be shown."From the added comment:
With regards to the TODO, it might make sense to just intentionally keep the current behavior: always forward
wShowWindow
ifSTARTF_USESHOWWINDOW
is set regardless of the subsystem of the process, since it doesn't seem like a program compiled with the console subsystem would care aboutnCmdShow
, or if they do, then I'm not sure why it makes sense to not setnCmdShow
.Tested the Windows behavior with the following setup:
Compiled with:
Compiled with:
and
(the STARTUPINFO returned from
GetStartupInfo
has thewShowWindow
of the CreateProcess call, butnCmdShow
passed to WinMain isSW_SHOWDEFAULT
)If the
si.dwFlags |= STARTF_USESHOWWINDOW;
line inlaunch-show.exe
is commented out, thennCmdShow
inWinMain
is alwaysSW_SHOWDEFAULT
.