Ignore this post - fixed it. Pretty new to GDI and certainly out of practice with unmanaged frameworks (I'm used to C#, Java, Rails, etc...) Rather than call DeleteObject (which according to the documentation should release all resources related to a bitmap) I simply use the delete keyword instead. Strange thing is delete keyword on a HBITMAP doesn't work and for that I have to use DeleteObject(). So the following code does demonstrate that there is no leak: void LoadI
Henners_666
I'm currently writing a docklet and as part of my configuration dialog I am attempting to load an image to a static picture control but I noticed there was a memory leak. Anyway to cut a long story short, I cut all the code down to the bare minimum and isolated the leak to the call to DockletLoadGDIPlusImage - now all I have in the method call I am making is the following: void LoadImageIDC_CLOCK(DOCKLET_DATA *lpData, HWND hDlg) { Bitmap *bmpHandle = DockletLoadGDIPlus
Thanks for the quick reply littleboy Checked the path and it was actually Docklet/DotNetDocklets2, however renaming it to the suggestion has no effect (incidentally it does detect all 3 docklets). My version of the .Net Framework is correct (Version 2.0.50727 SP1) Ah, that's excellent if you are releasing the code perhaps I should wait till the code is available and debug it to
Hi Littleboy, I am currently writing a docklet in C++, however I was interested in looking at using C# and your component would be ideal for that. However I downloaded the files from the link you gave but when I run the "Docklet Chooser dialog" it states for every sample docklet that "This docklet is not a valid .Net Docklet". Maybe I'm going blind but I couldn't see anything obvious that I'd missed - is this a bug? Regards.
Actually for Outlook if you pass through the /recycle switch as an argument you can force it to use the open instance if there is one