If you're getting dithering, then your bits per pixel may be set to less than 24 bits. Like I said, the device drivers do most of that work. GDI+ doesn't really make any decisions. I've never seen reliable results in alpha blending from GDI+. I avoid it and either write my own code to do it, or use OpenGL.

Yeah, i did that earlier, didn't help, but now things seems to be back to normal again, i suspect the DNS server(s) got updated. > The problem with computers is that they do what you tell them to do and not what you want them to do. < > If it doesn't matter, it's antimatter.<

Hey, Sorry... I assumed that you already knew all that. Some old posts: what will happen when i terminate a process?[^] Handling a process termination.[^] Anyway... could you give me some details about the environment that you intend on using this code? In my case... I was working with special devices with a customized embedded XP and I had control over the operating system... because we designed the OS. I guess what I am asking... is... are you in a similar situation or do you intend on attempting to block this on a standard Windows box. Doing this is an extreme hack... and I would only recommend attepting this in a controlled/closed environment. Did you hook both NtTerminateProcess and Endtask inside task manager? You can simply ignore the WM_CLOSE message in the target application... or perhaps hook SendMessageTimeoutW and simply return TRUE if the window handle is owned by the target process. I think I used an AppInit DLL to accomplish this on the embedded XP platform. Keep me informed on your progress... I have been *extremely* busy the last few days but I expect to be finished soon and have some free time starting Friday and through the next weekend. What I wanted to do was grap my old DLL and install it into a Windows7 VM to see if it worked there. I highly doubt anything has changed... when you open the task manager it executes under the credentials of the currently logged in user... If you want... click 'Email' in my reply and maybe we could collaborate and share some code. Best Wishes, -David Delaune

Hi, Sorry about the late reply. It's the Thanks Giving holiday here. It has also been 7 years since I wrote the above comment which appears to be completely correct. arnoudmulder wrote: In a remote desktop session on same computer the return value is zero. The odd thing is, in Windows 10 it also returns 0, odd because you would expect once it was supported it will stay supported. I believe that this CDC::GetDeviceCaps behavior over "Remote Desktop" is because your code is not using the physical hardware display driver. I believe over RDP you are actually using the "RDP Encoder Mirror Driver" object located at (%WinDir%\system32\drivers\rdpencdd.sys) which does not have hardware acceleration. In other words... the return value from CDC::GetDeviceCaps is correct. Best Wishes, -David Delaune

Thanks for your reply. What i ended up with was to use Gdiplus' GraphicsPath and its WidenPath (at the time i wrote the question i didn't realize Gdiplus had this too, i only knew about the GDI one). This one seems to work much better then the "simple" GDI implementation. Once again, thanks for the reply. > The problem with computers is that they do what you tell them to do and not what you want them to do. < > If it doesn't matter, it's antimatter.<

I'll give it a spin, thank you. > The problem with computers is that they do what you tell them to do and not what you want them to do. < > If it doesn't matter, it's antimatter.<

This is funny :) it gave a smile in my almost sad face. Come to think of it...why does the fairy give two wishes? Why not just one and then we'd wish we'd had a hundred wishes...that will go a long, long way.

The idea was good, thank you. Indeed sometimes all people need is a kick in the right direction and then they can tumble down the stairs themselfs. :) Most of the time i am just looking for that kick when asking questions, getting the complete solution on a plate is no fun. > The problem with computers is that they do what you tell them to do and not what you want them to do. < > //TODO: Implement signature here<

cmk wrote: The fact that it's open source alleviated any concerns about installing as admin ... or do you mean concerns for deploying to your customers ... yes, I could see that being an issue. -that's what i meant About the lingering, it's really nothing serious, it's just an "eccentric" thing of me, i can live with it. :) > The problem with computers is that they do what you tell them to do and not what you want them to do. < > Leela: Fry, you're wasting your life sitting in front of that TV. You need to get out and see the real world. Fry: But this is HDTV. It's got better resolution than the real world < >Nothing is free in the universe.<

No, i use TrackMouseEvent[^] to detect when the mouse leaves. Guess i'll have to go with the activation "relaying" then. Thanks for your help. > The problem with computers is that they do what you tell them to do and not what you want them to do. < > Leela: Fry, you're wasting your life sitting in front of that TV. You need to get out and see the real world. Fry: But this is HDTV. It's got better resolution than the real world <

Thanks for the suggestion but not in this situation. Basicly what i have is (something similar to) a "grid" of rectangular cells, each cell displaying textual information for the user, the user can resize this "grid", and i would like to present him as much information as i can when he "shrinks" the whole thing. Displaying a scrollbar wouldn'd be really usefull here i guess. The user will have tooltips to aid him but the more he can determine by just looking at the thing the better it should be. > The problem with computers is that they do what you tell them to do and not what you want them to do. < > Leela: Fry, you're wasting your life sitting in front of that TV. You need to get out and see the real world. Fry: But this is HDTV. It's got better resolution than the real world <

Thanks for the info. > The problem with computers is that they do what you tell them to do and not what you want them to do. < > Leela: Fry, you're wasting your life sitting in front of that TV. You need to get out and see the real world. Fry: But this is HDTV. It's got better resolution than the real world <

you're welcome. :) Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.

In the actual code there are more then one event i am waiting for that is why you see WaitForMultipleObjects, i just simplified the code for simplicity. And yes, i am sure that the event signalling the overlapped operation completion is fired, it is the very first event handle inside the array passed to the wait function and i get WAIT_OBJECT_0 from it. Most of the time this seems to be working ok but time to time... > The problem with computers is that they do what you tell them to do and not what you want them to do. < > Leela: Fry, you're wasting your life sitting in front of that TV. You need to get out and see the real world. Fry: But this is HDTV. It's got better resolution than the real world <

As the documentation[^] states: "Enables an application to supersede the top-level exception handler of each thread of a process.", so i don't have to explicitly set this up for every thread, and it seems to be working too (mostly at least). > The problem with computers is that they do what you tell them to do and not what you want them to do. < > "It doesn't work, fix it" does not qualify as a bug report. < > Amazing what new features none of the programmers working on the project ever heard of you can learn about when reading what the marketing guys wrote about it. <

When you need P/Invoke (managed code calling native code), this article of mine[^] might be useful. :) Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.

Thanks but i don't see how this answers my question...please clearify and sorry for my ignorance. > The problem with computers is that they do what you tell them to do and not what you want them to do. < > "It doesn't work, fix it" does not qualify as a bug report. < > Amazing what new features none of the programmers working on the project ever heard of you can learn about when reading what the marketing guys wrote about it. <