generic_user_id wrote: Anyway, thanks for the effort Jeffry. I tried.... I have been dual monitor so long, I think I have experienced (almost) every bug in existance related to nView (and a few in ATI, though I only used two ATI machines in 6 years). glad you fixed it! :) _________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)

I'm not arguing with any of these points, just saying that in this day and age, I doubt anyone will notice the difference :-) Christian I have several lifelong friends that are New Yorkers but I have always gravitated toward the weirdo's. - Richard Stringer

BTW, Since you plan to poll you should do it at least double the maximum possible expected input frequency to ensure you do not miss a pulse. Col :-)

My mistake, I meant to say that GetLastError() returned 0, just after I attempted to create the hook. I thought I had to place the procedure in a DLL only for system-wide hooks, but it appears it's in order for all hooks outside of the calling process. Griffith Everything you say will be misquoted, ripped out of context and used against you.

Okay, I'll try that then. I know for sure it's possible to read the memory of existing processes though. Thanks a lot guys Griffith Everything you say will be misquoted, ripped out of context and used against you.

Thanks a lot! Everything you say will be misquoted, ripped out of context and used against you.

Ahh thanks, that must've been the problem. It's strange I never read the platform SDK was required. (Most things compiled fine without it). And I still have the impression it wasn't worth the 200mb download... Thanks a lot for helping me out, Kind regards, Griffith Everything you say will be misquoted, ripped out of context and used against you.

I just tried this today and got the same error. Unfortunately, I do not know why either. I think (but am not sure) that maybe WTL7 is for .Net and that is why it may not work. I believe that there is an ATL 2.0, ATL 3.0 and 7.0 and a WTL 3.0 and WTL 7.0. The only thing I can figure, since there seems to be a major jump in version numbers, is that 7.0 is for .Net. Can someone clarify or verify this?

The other one i got and use. It is far from the MSDN help, but still better than searching trought the headers. The first link had a link to the other tutorials i was trying to remember before though. They are here clipcode /:cool: - Don't sweat the petty things, and don't pet the sweaty things.

I've read "Win32 Programming" by Brent Rector and Joseph M. Newcomer. It's an excellent read and a great reference book. My copy started to fall apart because I used it so much when learning pure Win32 programming. Also, Joseph is a registered CPian and well-respected programmer. Take a look at some of his articles to see the quality of his work. This is also reflected in the book. Jeremy L. Falcon Homepage : Sonork = 100.16311 "Victims falling under chains ~ You hear them crying dying pains The fist of terrors breaking through ~ Now there's nothing you can do" Song: Phantom Lord - Album: Kill 'em All - Artist: Metallica

Then that sounds like either (1) a serious bug in the RE Control, or (2) a redraw problem.    Peace! -=- James. "Fat people are hard to kidnap." (Try Check Favorites Sometime!)

Good idea. I'll try that Thanks for the feedback!

[nt]

Oops, I answered the wrong question of myself here. :) My solution to this one was pretty cheap, I just made a counter (structure with HTREEITEM and an INT) and every time an item was added to a part of a tree I updated the counter. As the user could not add or delete things from the tree, this solution worked quite well. I used GetItemtext(..), added "(%d)" to the string and set the new string with SetItem(..) But I take it this was not the 'obvious' solution :)

Okay, thanks. I guess I have to do it in the dirty way, as there appears to be no proper solution. But as the desktop is a class of some sort it should be possible to create an array of them. I wonder why it isn't an array of desktops in the first place....

Of course, your connection has to be stable. I pinged some random servers, and with 30000 or so pings, the lowest and highest are less than 20 ms apart. And if the program is a little smart, it will notice when the ping changes (upstream in other PC on LAN), so it will adjust the timeout settings. I believe nothing like this is made so far, and I think it might work real well. The program mainly avoids package loss on otherwise stable connections. Thanks for you feedback, let's hope some more CPers will give their opinion.

Sorry, that was a typo, I compiled it with SetWindowLong in the other handler. The SetWindowLong line doesn't make a difference, nothing happens at all. (at least nothing directly visual) Even without the SetWindowLong call the borders of the NC area aren't painted at all. The border doesn't get painted, but that didn't happen in the first place, my problem was that not only the buttons were painted, but a small area around the buttons too, and there is a line drawn that seperates the client and the non-client area. If I don't make a handler to NCACTIVATE at all windows paints the NC area as soon as it looses focus, otherwise not. Maybe I didn't make myself entirely clear, but I would like windows to paint nothing at all outside of the client area, as windows refuses to draw the button without background. Heh, this isn't as easy as I thought it would be, even explaining a simple problem can be quite hard.

Griffith Sutherns wrote: Also, I'm not quite sure where to put the SetWindowLong(hDlg, DWL_MSGRESULT, FALSE); you mentioned This goes in your WM_NCACTIVATE message handler. Inside of your DLGProc, and dialog proc cannot return the result of the message the same way a window proc does, therefore you need to call set window long and set the result there instead.

Thanks! That might be what I'm looking for.