| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | TWO PROBLEMS. |
Hello ERIC! In a message written on Thursday June 08 1995, ERIC CARMODY insanely babbles to PAUL SIDORSKY: EC> WinSetWindowPos( winhwnd, HWND_TOP, 0,0,0,0, SWP_ZORDER ); EC> This is done every 3 seconds in my timer loop which is in my timer EC> thread. Its much easier to have a thread which just loops rather than EC> trying to work in a call to WinSetWin... into your main program logic. Hmmm, I'll have to give this a try. It definitely sounds easier than trapping messages, especially since I already have a thread running that I can put this into. However, it also sounds like it may strain the CPU a little (well, only about 5% for a half second, but I am worried about that since I want to keep my program's CPU usage as low as possible), and it also sounds like it won't keep the window "Always On Top", just "Mostly On Top". What I mean is that if the focus changes right after the call to WinSetWindowPos() has happened, it won't get back on top for another 3 seconds. This isn't too big of a deal, but I would prefer to do it more seamlessly if possible. At any rate, thanks for the tip, and I'll give it a try. If anything it'll be good for me while I'm testing, especially because it's so easy to implement. -- PaulS --- FMail/386 1.0g* Origin: C.R.I.S.I.S. HQ, Calgary AB, (403)686-0449, 28800 V.FC (1:134/31) 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: 134/31 17 3615/50 396/1 270/101 105/103 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™.