WPF

Collin Jasnoch wrote:

Soo how do you expect the IEditableObject to do this work??? (if you read Pete's
blog he even says that his EditableObject uses reflection....). Also reflection
is not that slow. I mean if this has to occur over and over (like 100's of time
in seconds.. why would this be though???) and the object is very large (consider
refactoring) you may want a different option (again.. I do not see how the
IEditableObject solves this.. it is merely an interface, NOT an implimentation
of it).

Collin Jasnoch wrote:

So were you planning on binding some UI elements to private properties??? Or
'Complex' properties as you put it? If so, the logic is already there... Because
you already implimented it. Also, if you want it to support private fields you
can certainly impliment that (I did not because I had no need for it)

Collin Jasnoch wrote:

Do you really think the OP requires this anywhere???

Collin Jasnoch wrote:

On a last point, even if you provide a nice implimentation of IEditableObject
(that somehow does NOT use reflection), you are now forcing a base class on an
object for simple functionality (see post above.. what like 10 lines of
code).

public static BitmapSource MakeTransparent(this MemoryStream stream)
{
  Bitmap bitmap = new Bitmap(stream);
  bitmap.MakeTransparent();
  return Imaging.CreateBitmapSourceFromHBitmap(
      bitmap.GetHBitmap(),
      IntPtr.Zero,
      Int32Rect.Empty, 
      BitmapSizeOptions.FromEmptyOptions()
    );
}

var bitmap = new System.Windows.Media.Imaging.BitmapImage();

MemoryStream stream = new MemoryStream();
img.Save(stream, ImageFormat.Bmp);
stream.Seek(0, SeekOrigin.Begin);
 bitmap.StreamSource = stream;

Bitmap bitmap1 = new Bitmap(stream);
bitmap1.MakeTransparent();
return Imaging.CreateBitmapSourceFromHBitmap(
      bitmap1.GetHbitmap(),
      IntPtr.Zero,
      Int32Rect.Empty,
      BitmapSizeOptions.FromEmptyOptions()
);