| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | WinCancelShutdown |
Thanks Jonathan de Boyne Pollard for your msg about WinCancelShutdown, on Thursday, 11-17-1994! JP> Since (in theory) windows are "owned" by anchor blocks, and each JP> thread has its own anchor block, I'd then expect the WM_QUIT to arrive JP> on the message queue of the thread that created the window. JP> So would I, but I got started down this road because I read in about three different places that it was very important to call WinCancelShutdown() on all threads but the one that you want to handle the WM_QUIT or dire consequences (a lockup) could occur. So, of course, I wanted to find out what da deal since we have very many threaded, PM apps. The warnings I have read is that the system will basically just pick a queue at random and post the WM_QUIT. But that certainly does not seem true. But it seems that no one really knows the facts here. A few people have responded on Compuserve but they don't seem to know as much as I already do or seem to have theories of their own that don't seem to fit my experiment results. Sooooo.... I'm not sure really how to go now. I'm certainly not going to do the massive amount of work it would take to implement this right now unless I know for sure that I'm going to get something out of it. ___ X KWQ/2 1.2b X If at first you don't succeed, put out another version (KWQ 1.2). --- Maximus/2 2.02* Origin: Fernwood - your source for OS/2 files! (1:141/209) SEEN-BY: 12/2442 54/54 620/243 624/50 632/348 640/820 690/660 711/409 410 413 SEEN-BY: 711/430 807 808 809 934 942 949 712/353 623 713/888 800/1 @PATH: 141/209 270/101 396/1 3615/50 229/2 12/2442 711/409 54/54 711/808 809 @PATH: 711/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™.