Paint.NET v3.5.9 Beta (build 4278) is now available

This is a minor update to Paint.NET v3.5. It has some bug fixes, and also adds back in the Korean translation (thanks to Bing translator).

As usual, you can download it directly from the website or you can use the built-in updater. Make sure that you enable “Also check for pre-release (beta) versions”, which you can do by going to Utility –> Check for Updates, and then clicking on the Options button.

Here’s the changes from v3.5.8:

  • Improved: The "Auto-detect" bit-depth setting for PNG, BMP, and TGA now also determines which bit-depth to use based on which one produces the smallest file size, as well as which ones can save the image without losing fidelity.
  • Improved: You can now use Ctrl+0 as a shortcut key for View -> Actual Size, in addition to Ctrl+Shift+A and Ctrl+Alt+0.
  • Fixed: Some text in the DirectDraw Surface (DDS) Save Configuration UI was not being loaded.
  • Fixed: Some DirectDraw Surface (DDS) files authored with other software (e.g. Unreal 2004) could not be loaded.
  • Fixed: In some rare circumstances, clicking on the Save button in the toolbar would crash.
  • Fixed: The Korean translation has been added back in, with the help of Bing machine translation to cover the few remaining strings that were untranslated.

As for 4.0, progress has been slow the last few months because I’ve been rather busy at work. I work at Microsoft in Windows on a little project called Windows Performance Analyzer (formerly known as “xperf” in some circles). The new version has a completely new UI written using WPF. Our PM, Michael Milirud, presented this at BUILD last week: . I highly recommend checking it out, although I’m biased of course Smile

One of the features I’m planning for 4.0 is tentatively titled “Shapes.” Right now you can only draw rectangles, ellipses, lines, and (admittedly lame) freeform polygons. Even MSPaint in Win7 has a larger shapes library. The idea I’ve got is to ship with a much larger list of built-in shapes, but also to allow users to install new shapes (from the forum, or their own imagination, or from wherever). The idea is to use XAML as the serialization format, and to make it compatible with WPF’s Drawings and Geometry objects. This way you can use any existing XAML editor to create the shape. (And this also means I don’t have to write an authoring tool!)

I already have the data format working – I have my own Geometry classes that wrap Direct2D, and was able to get them to roundtrip using XamlServices from System.Xaml.dll (I was quite amazed really – it worked the first time!). Since WPF and Direct2D use the same object model for their Geometry classes, it should be no trouble to auto-convert from WPF XAML files, thus eliminating the need for little annoying conversion utilities. So a XAML shape could use either the Paint.NET Geometry classes, or WPF’s. Probably sitting in a ResourceDictionary. Now, Geometry objects only describe shape outlines, with no fill or stroke parameters. The next thing is to add “Drawing” support. Each element of a Drawing contains a Geometry*, but also includes details about stroke color, stroke thickness, and a fill brush. Imaging you have a vector version of a company logo, with specific brush stroke and fill colors. You could plug that into Paint.NET and use it to draw. And yes, you’d be able to use solid colors as well as gradient brushes.

* In WPF, a Drawing can also contain other elements such as bitmaps or text or whatever.


14 thoughts on “Paint.NET v3.5.9 Beta (build 4278) is now available

  1. metadea says:

    Dear Rick,

    i have seen source codes of a previous version of (i think it was 2.x). i remember that you have created an abstract base class for layers, so would it not be possible to differ between vector- and pixellayers? the tools could have a property that indicates if they are vector or pixeltools, so that they’re enabled/disabled in their case.

    it would be very cool to have this difference, so that you don’t have to remove previously done minor errors like 1 pixel too big rectangles or that you don’t have to rewrite complete text areas, because of a forgotten comma.

    Thanks for reading.

  2. John Dangerbrooks says:

    “I work at Microsoft in Windows on a little project called Windows Performance Analyzer”

    Oh, I see. So you are the guy that Microsoft Support personnel were hopping me bump off out of frustration! 😉 There was a period of time in which whenever I contacted Microsoft Support because I had a trouble, they asked me to get xperf. Downloading xperf is a torture, especially on a troublesome computer.

    I never got xperf. I just took my copy of Delphi and created something that helped me out.

    P.S. The “bump off” thing was a joke.

    • Romanos Nianios says:

      I dont believe that microsoft will get rid of .NET/C#/C++ in the next at least 5 years, because so many apps is based on them , and dont forget that in .net framework there is also the asp framework which enables so many webpages and web tools.

      • Rick Brewster says:

        I think even if they stopped development on .NET entirely, and deprecated the whole dang thing, they’d still make it available and support it for another decade or two. I work at Microsoft, and while I don’t have any “inside info” on this, I can’t imagine they/we would just tell all developers they have to throw away the last decade of their work.

  3. Romanos Nianios says:

    I am new in .NET programming and programming overall so i dont know how that models works thats why i said at least 5 years. By the way 2012 is near 😛 any update on 4.0 ? I love your programm and i used it to make professional work , its simplicity is superb. I hope the best for you and your program.

Comments are closed.