WriteableBitmapEx

New Post: Resizing Image distorts its pixels around corners

Tehreem — Sun, 19 May 2013 19:00:13 GMT

Hi!

I needed to resize an image so I used following code:

            WriteableBitmap img2 = new WriteableBitmap((int)width, (int)height);
            img2 = img.Resize((int)width, (int)height, WriteableBitmapExtensions.Interpolation.Bilinear);
destination.Blit(new Rect(coords.X, coords.Y, img2.PixelWidth, img2.PixelHeight), img2, new Rect(0,0, img2.PixelWidth, img2.PixelHeight));
            return destination;

But when i save this destination image it becomes distorted around the edges and gives me this image:

Any ideas for what can be wrong here?

Closed Feature: Add Fill methods [11053]

teichgraf — Thu, 16 May 2013 11:36:54 GMT

Implement various Fill*() methods as addition to the Draw*() methods like FillEllipse(), FillRect(), ...

Closed Feature: Add parametric Curve method [11054]

teichgraf — Thu, 16 May 2013 11:36:53 GMT

Implement a DrawBezier() and DrawCurve() method to support parametric curves / splines.

Closed Issue: Clip DrawEllipse at boundaries [12552]

teichgraf — Thu, 16 May 2013 11:36:53 GMT

See [discussion:208643]
http://writeablebitmapex.codeplex.com/Thread/View.aspx?ThreadId=208643

Closed Feature: 90° Rotate methods [13362]

teichgraf — Thu, 16 May 2013 11:36:53 GMT

To make the transformation methods complete, a Rotate method should be added with support for 90° steps.

Closed Issue: Bug on WriteableBitmapExtensions.cs [13563]

teichgraf — Thu, 16 May 2013 11:36:52 GMT

At line 63, actual code:
int h = bmp.PixelWidth;

Right code:
int h = bmp.PixelHeight;

Closed Feature: Flip methods [13816]

teichgraf — Thu, 16 May 2013 11:36:52 GMT

Implement FlipHorizontal and FlipVertical methods.

Closed Issue: GetPixel Bug? [14151]

teichgraf — Thu, 16 May 2013 11:36:52 GMT

I think I found a bug in GetPixel, there are some casts missing for retrieving the colour components. You should be able to reproduce the issue by looping over the pixels and doing bmp.SetPixel(x,y,bmp.GetPixel(x,y))

WriteableBitmapBaseExtensions.cs Line 170
return Color.FromArgb(a, (byte)((c >> 16) * ai), (byte)((c >> 8)* ai), (byte)(c * ai));
Fix:
return Color.FromArgb(a, (byte)((byte)(c >> 16) * ai), (byte)((byte)(c >> 8)* ai), (byte)((byte)c * ai));

I did try to create and upload a patch but for some reason the mime type of the file was jpeg, I don't know if that is because my TortoiseSVN is slightly out of date or if the problem lies elsewhere.

Closed Task: Windows Phone release [14361]

teichgraf — Thu, 16 May 2013 11:36:52 GMT

Starting with version 1.0 a ready-to-use WP7 built should be provided.

Closed Feature: Add Convolute method [14796]

teichgraf — Thu, 16 May 2013 11:36:51 GMT

Add the Convolute method as suggested here
http://writeablebitmapex.codeplex.com/Thread/View.aspx?ThreadId=236374&ANCHOR#Post528218

Todo:
The alpha value should be preserved.
Use rectangular array as kernel parameter to avoid kernelwWdth and kernelHeight parameters.
Optimizations.
The values should wrapped at the borders.

Closed Issue: DrawLine is not working correctly for boundary points [14941]

teichgraf — Thu, 16 May 2013 11:36:51 GMT

The DrawLine method is not drawing all the points between the starting (x,y) point and the ending (x2,y2) points. For example you can create a new WriteableBitmap having (10,10) size and try to draw the line from (0,0) to (9,9). The latest point (9,9) will not be affected by the DrawLine method. I suspect there is a boundary check which stops drawing before the ending point is reached.

Closed Issue: Bug in Crop when width/height is same as the source width/height [15084]

teichgraf — Thu, 16 May 2013 11:36:51 GMT

When using the .Crop function with the same width (or height) as the source width (or height) , the returned result is one pixel smaller.

Dim img As New WriteableBitmap(100, 100)

Dim img2 As WriteableBitmap = img.Crop(0, 0, 50, 50)
'Correct : returns a 50x50 image

Dim img3 = img.Crop(0, 0, 100, 50)
'Bug? : returns a 99x50 image , expected 100x50

Closed Feature: Free Rotate Methods [15214]

teichgraf — Thu, 16 May 2013 11:36:50 GMT

In addition to the 90° fixed methods, support for any angle should be added.
Follow up to http://writeablebitmapex.codeplex.com/workitem/13362

Closed Issue: FillRectangle off-by-1 [15515]

teichgraf — Thu, 16 May 2013 11:36:50 GMT

FillRectangle is drawing 1 extra pixel in the top right corner

WriteableBitmapFillExtensions.cs Line 85:

for (int x = startYPlusX1; x <= endOffset; x++)

Proposed fix:

for (int x = startYPlusX1; x < endOffset; x++)

Closed Feature: Make available as NuGet Package [15697]

teichgraf — Thu, 16 May 2013 11:36:50 GMT

Nothing more to say... would be great if the package would be available as a public NuGet package for easier / quicker installation (yep, I'm this lazy! ;-) ).

Closed Issue: FillEllipseCentered hangs when radius is zero [16074]

teichgraf — Thu, 16 May 2013 11:36:49 GMT

In that case, I would simply expect nothing to be drawn :)

Closed Issue: FillRectangle draws a one-pixel line at the edge when it is out of bounds [16075]

teichgraf — Thu, 16 May 2013 11:36:49 GMT

bmp.FillRectangle(-10, 10, -5, 20, Colors.Red) produces a vertical line (0, 10)-(0, 20). Same applies to all other edges as well.

Closed Issue: DrawPolyline points not connected [16201]

teichgraf — Thu, 16 May 2013 11:36:49 GMT

As you can see in the attached file "polyline-points-not-connected.PNG" (as well as in the second example) the line between certain points inserted into the DrawPolyline aren't always connected. This makes it difficult for the user to recognize an actual data point.

The following array of data was inserted into a WriteableBitmap of 1375x400:
50,349,60,349,71,350,82,350,92,116,103,140,114,334,124,346,135,348,146,348,157,349,167,349,178,348,189,349,199,349,210,349,221,350,231,349,242,349,253,349,264,349,274,349,285,346,296,347,306,105,317,342,328,349,338,349,349,349,360,349,371,349,381,346,392,348,403,348,413,348,424,349,435,350,445,350,456,350,467,350,478,-341,488,334,499,346,510,349,520,348,531,348,542,349,553,346,563,343,574,344,585,346,595,348,606,346,617,326,627,348,638,348,649,349,660,350,670,348,681,349,692,346,702,344,713,348,724,346,734,343,745,347,756,335,767,346,777,348,788,349,799,349,809,349,820,349,831,349,841,350,852,350,863,348,874,350,884,349,895,350,906,349,916,349,927,349,938,349,949,349,959,349,970,348,981,349,991,343,1002,335,1013,340,1023,349,1034,349,1045,349,1056,350,1066,350,1077,349,1088,349,1098,341,1109,349,1120,349,1130,349,1141,350,1152,348,1163,332,1173,343,1184,350,1195,350,1205,349,1216,347,1227,350,1237,349,1248,348,1259,346,1270,191,1280,-510,1291,338,1302,350,1312,347,1323,350,1334,348,1345,348

Also, thanks a lot for the classy extension.

Edit:
Old ticket replaced (but attachment remaining); I was fairly sure I was using the latest version but apparently I wasn't and updating solved that but introduced a new issue.

Closed Issue: Nuget Package with strong Name [16636]

teichgraf — Thu, 16 May 2013 11:36:48 GMT

Could you Sign your assembly on nuget.

Thanks

Closed Issue: FillRectangle throws IndexOutOfRangeExceptions [16810]

skalkin — Thu, 16 May 2013 11:36:48 GMT

... when negative coordinates are passed. This is the bug introduced in the latest version, the stable version works well.