Snowprog77 wrote: What benefits do I get from the second approach? Is it faster? For me it looks like I just put one more step in the row. Is there less flickering? Yes - graphics hardware has highly optimised bit-blit operations, which is precisely what's used to move the off-screen surface to the device. Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p

Due to short-circuit of the boolean operations inside the if statement, the code is reasonably fast. Maybe using three look-up tables will improve the code speed, but I'm not an expert. :) If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile. This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke [My articles]

You can use the DllImportAttribute[^] to specify the CallingConvention[^], but I don't think .Net will marshal STL strings to a String. You would probably have to specify those parameters as an IntPtr, then convert the code from this[^] article to C# (it's shown in the "Converting String to std::string" section). Take care, Tom ----------------------------------------------- Check out my blog at http://tjoe.wordpress.com

Does arabic really work with totally mirrored desktops? I didnt keep this in mind :-(

Thanks for your hint. But I knew already that I can use pointers and I also used code simiar to the example. What I dont like in this solution is the "byte per byte" transfer to the new buffer. Isnt there a way to copy a complete block (like in C++ "memcpy" wich should be faster than a byte per byte transfer)? Thanks again Snow

Thanks thats what i wanted ;-)

Thanks a lot!

Thanks for your answer Tim. I found an MSDN article "Thread Safety in the Standard C++ Library" which statet that some of the STL container classes are threadsafe (but only in certain cases). But I think it will be better to write a wrapper for the queue class as you wrote before. It seems to be the only way to be on the safe side. Thanks, Snow.

Your only option is to run a message pump on that thread also, using the Application.Run[^] method. public Form1() { fm = new Form(); Application.Run(fm); } Regards Senthil _____________________________ My Blog | My Articles | WinMacro