Bitmap.Clone() thread safety
You are wrong, look:Bitmap and Image constructor dependencies http://support.microsoft.com/kb/814675/en-usand try this: public void BmpTest() { Size s = new Size(80, 60); int imgSize = s.Width *...
View ArticleBitmap.Clone() thread safety
I've recently discussed the matter with MS support, since this has been causing me problems. What follows is a combination of what I've learned from them and what I've observed myself. 1) While...
View ArticleBitmap.Clone() thread safety
The Bitmap.Clone() method is implemented as a deep copy. It creates a completely new bitmap that has no reference to anything from the original Bitmap object, so the answer is yes. David: beware that...
View ArticleBitmap.Clone() thread safety
Let me clarify my earlier statement upon re-reading of your original post. Bitmap.Clone() creates a new reference. So it is safe to use.
View ArticleBitmap.Clone() thread safety
Bitmap.Clone() should be threadsafe, as the clone method only refers to the current object. Use it as follows: Code Snippetbitmap2 = (Bitmap)bitmap1.Clone();
View ArticleBitmap.Clone() thread safety
Is it safe to use the output of Bitmap.Clone() on a separate thread? Or do I need to force a deep copy (make a new bitmap and blit over the contents) to make sure it works right?
View Article
