Even if you obfuscate function names, your obfuscator tool should be able to convert the obfuscated stack trace to original stack trace. Use Crypto Obfuscator (although not free) which supports this. But if you want, it can also keep your function names intact and do other obfuscations like string encryption, control flow obfuscation, method call hiding, etc.

First of all: Thanks Tim for the time you spent on the answers! I appreciate that very much. You gave me some interesting issues to think about. I hope, you'll do further well with the cones and the Robots ;-)

I am not sure if something is getting lost in translation. Do I understand you correctly, the code you posted is written in MS Word's own code editor (i.e. it is VBA), or has it been written in VB.NET using Office.Interop? My advice is free, and you may get what you paid for.

cherrymotion wrote: I have no possiblity to change the incoming char-ptr (because I get it sent on my interface). Then you need to copy the pixel data to a properly row-aligned array. You could use the Bitmap(Int32, Int32, PixelFormat) constructor and copy the incoming data row-by-row to the new bitmap's data. Mark Salsbery Microsoft MVP - Visual C++ :java:

I've personally always kept regions of interest separate from the image, just drawing the ROIs at render time instead of drawing on the actual image data. A couple possibilities: 1) Use double buffering. Use a graphics object created for a bitmap with the same bit depth as the screen. Draw the image to the graphics, draw the ROIs on the graphics, and render the bitmap to the screen. 2) Use GDI directly via platform invoke. Mark Salsbery Microsoft MVP - Visual C++ :java:

What you can do is have a flag variable that keeps track of whether the delegates are initialized. Then, in every exported function, the first thing you do is check to see if the delegates have been initialized. If they have not been initialized (according to the flag variable,) then you call the initialization function from there. That way, the initialization is performed on the thread that is calling your Dll, instead of the thread that is calling DLLMain.

A Forms.Timer is like a Control, you should only touch it from the main thread, hence outside your worker threads. It needs an Interval value, a Tick handler, and a Start(). It is best to make the timer object a class member of your Form (or other Control). :) Luc Pattyn [Forum Guidelines] [My Articles] DISCLAIMER: this message may have been modified by others; it may no longer reflect what I intended, and may contain bad advice; use at your own risk and with extreme care.

Thanks a lot you people! I'm very happy of always getting such good answers. Respect, for me you are number #1 in the web! On Topic: I'll test your way to create bitmap tomorrow, it's late in europe right now ;-) It looks good, but I remember some problems as I wanted to get it done like that. The cam I use is a monochrome Leutron PicSight P52M-USB, and the only way I get monochrome Bitmaps done is to assign the Format8bppIndexed - which further made some problems in resizing, so that I have to work with a temp-Image. I'm not happy with that, but I didn't get a better way yet. I'd be more happy with not having to work with marshaling between managed and unmanaged. But my company has "old" native interfaces (one for graphic, one for cam), which must not be changed. So I had to delegate all function (the way I got it done is also from codeproject) - but it seems to me as a not very stable solution, to call a managed GUI in creating a thread from native and so on... Maybe someone wonders about an odd comment, please let me know. I may be on the wrong way somewhere... Thanks again for your time, bye!

Don't know why I didn't think of that. :) I've spent a good part of this week working on resizing the cells in the TLP!

Hi, The Form class already has 4 events regarding resizing: Resize, ResizeBegin, ResizeEnd, SizeChanged. That should cover it I'd say. However you have to keep the current Size somewhere in order to calculate growth/shrink. :) Luc Pattyn [Forum Guidelines] [My Articles] The quality and detail of your question reflects on the effectiveness of the help you are likely to get. Show formatted code inside PRE tags, and give clear symptoms when describing a problem. modified on Friday, May 22, 2009 3:48 PM

I am not sure why Refresh didn't worked for you. When you call Invalidate(), it just invalidates the client area. It will not repaint immediately. It will be repainted when the control receives a WM_PAINT message. So Invalidate() is not synchronous. Refresh just calls other overload Invalidate(true) and Control.Update to force paint on the control. This is synchronous and you can see the effect immediately. I tried your sample and Refresh worked just fine on my machine. :) Navaneeth How to use google | Ask smart questions

There's a bunch of things wrong there :) First you NEVER use a CPaintDC except in response to WM_PAINT (in OnPaint()). A CPaintDC is not valid in any other place. Second, I can't tell how you're trying to create the bitmap, but your calls are out of order. I'm not even sure how to correct it without knowing what you want the bitmap to be. Third, there's no code shown that has anything to do with setting a picture control's bitmap, which I thought was the original problem. What are you trying to do? Mark Mark Salsbery Microsoft MVP - Visual C++ :java: