[NSIS-Bugs] [ nsis-Bugs-2796189 ] ExecWait doesn't always respect maximized window setting

[SourceForge.net <no...@so...>]

Bugs item #2796189, was opened at 2009-05-24 16:57
Message generated for change (Tracker Item Submitted) made by fatcerberus1
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=373085&aid=2796189&group_id=22049

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: General
Group: 2.0 Series
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Bruce Pascoe (fatcerberus1)
Assigned to: Nobody/Anonymous (nobody)
Summary: ExecWait doesn't always respect maximized window setting

Initial Comment:
Many applications save their window size and state with their settings, to be restored the next time they run.  However, calling ExecWait on such an application often results in the program starting up restored, rather than maximized, even if it was maximized last time you closed it.  After digging into the NSIS source, I discovered the reason for this: ExecWait is passing the process an SW_SHOWNORMAL window state, rather than what it should be passing, SW_SHOWDEFAULT.  SW_SHOWDEFAULT means "use the current window state", while SHOWNORMAL means "restored".  A common mistake for many developers to make, and hopefully one that's easily fixed. :-)

NSIS: 2.44
Operating system: Windows 7 RC (7100)


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=373085&aid=2796189&group_id=22049