| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Notebooks |
27 May 95 13:02, Jonathan de Boyne Pollard wrote to Steffen Offermann: >> Any idea, why closing a notebook causes my main application >> window to be closed as well? ... and what to do in order to >> prevent this from happening? JdBP> The default behaviour of WinDefWindowProc when it is JdBP> passed a WM_CLOSE is to post a WM_QUIT message to the JdBP> message queue for the window, which causes your JdBP> WinGetMessage/WinDispatchMessage loop to end. JdBP> When doing multiple window programming you almost *never* JdBP> want to pass WM_CLOSE to WinDefWindowProc. What should I do instead to get rid of the window that received WM_CLOSE if not having WinDefWindowProc() process the message? I do want to get my notebook window closed, I merely don't want it to end the whole message loop. Tschuess, Steffen --- FastEcho 1.41g+* Origin: Sprach's und verschwand von der Bildflaeche (2:2433/1860) SEEN-BY: 105/42 620/243 711/401 409 410 413 430 807 808 809 934 955 712/407 SEEN-BY: 712/515 628 704 713/888 800/1 7877/2809 @PATH: 2433/1860 1800 1200 225 2452/110 105/42 712/515 711/808 809 934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.