Sign in to follow this  
Rick Brewster

Paint.NET v3.20 *Alpha 2* is now available

Recommended Posts

>>A few Fit and Finish Requests for this version of Paint.net. Please. :D

[*]Remove the outline on the effect sliders, like it was before.<<

Yes, please.

>>[*]Update the icon of the image drop down menu<<

No, please.

>>[*].PDN file type icon<<

No need. Anyone who likes the file icons can download them and even a noob can learn how to change them manually via folder options. Plus, on vista the file type icon looks nice as it's per default, I think. I've made my own so they fit in the xp style and I like them how they are.

Another point that is important for me: I heard that the 1st Alpha "killed" the HD Photo plugin. Will the plugin work again in the final release or, as an alternative, will the plugin be updated? This is very important as I'd have to convert my HD Photo files back to PNG.

Remember that HDP is now becoming JPEG XR and Paint.Net should support it at least via plugin. I do not requesting more options, I only want that it does the same thing it does now: Open & save.

Share this post


Link to post
Share on other sites

Lovely update.

The biggest problem is that all the tuts will soon have to be converted to PDN 3.2.

Explain: By this I mean, all the effects are now enhanced in terms of UI and functinality. Y this, for example in a tut, there could be a step where you use Zoom Blur and a the time it was written PDN 3.10 was the latest where there 1 or was it 2 sliders but now, you've got more meaning all tuts are outdated.

Despite my complaint, this alpha release is radical.

Share this post


Link to post
Share on other sites

People will just have to use common sense when it comes to using the newer version plugins. If you're using the same plugin as the tutorial instructs to, then it shouldn't take too much to figure out what is still needed to be done. Anyhow, the sliders that were there before are still there now, only a few new variables have been added.

Share this post


Link to post
Share on other sites

New funtion only = New possibilities. :D

It does not mean the end of old tuts. :)

Share this post


Link to post
Share on other sites
Not gonna happen.

Party pooper. ;)

It would probably be fairly easy to implement, at least for plugins using the Property-based effect system.

Share this post


Link to post
Share on other sites

What have I said about saying stuff like, "it would be easy to implement" ... ? C'mon man. Don't say that. There's more to a feature than just writing a few lines of code.

Share this post


Link to post
Share on other sites

I love the new aspect/absolute size selectors for the Selection tool. Is there any way to include that on the Move/Resize Selection and Move/Resize Pixels tool, as well? Sometimes, I've drawn a selection and would like to resize it; I realize I can use shift+drag, but since the purpose of the new feature is easy discoverability, I think it should extend to the Edit Selection/Selected tools, too.

Share this post


Link to post
Share on other sites

This text file was created because Paint.NET crashed.
Please e-mail this file to paint.net@hotmail.com so we can diagnose and fix the problem.

Application version: Paint.NET v3.20 (Alpha 2 Release build 3.20.2871.36803)
Time of crash: 14/11/2007 15:36:53
Application uptime: 00:04:55.8437500
OS Version: 5.1.2600.131072 Service Pack 2 Workstation x86
.NET Framework version: 2.0.50727.832 x86
Processor: 2x "Intel(R) Pentium(R) 4 CPU 3.00GHz" @ ~3000MHz (SSE, SSE2)
Physical memory: 1023 MB
Tablet PC: no
Locale: pdnr.c: en-US, hklm: en-US, hkcu: n/a, cc: en-GB, cuic: en-US

Exception details:
System.NullReferenceException: Object reference not set to an instance of an object.
  at EdHarvey.Edfects.Controls.SplitButton.SetButtonDrawState()
  at EdHarvey.Edfects.Controls.SplitButton.OnEnabledChanged(EventArgs e)
  at System.Windows.Forms.Control.set_Enabled(Boolean value)
  at EdHarvey.Edfects.Effects.ThresholdEffectConfigDialog.histogramLoadWorker_RunWorkerCompleted(Object sender, RunWorkerCompletedEventArgs e)
  at System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(RunWorkerCompletedEventArgs e)
  at System.ComponentModel.BackgroundWorker.AsyncOperationCompleted(Object arg)
------------------------------------------------------------------------------

Looks like a plug-in escaped your plug-in crash system :)

Share this post


Link to post
Share on other sites

Im still yet to try Alpha 2, but I liked all the new things in Alpha 1. Mostly how a plugin crashing wont result in pdn crashing. Its not uncommon for a plugin to crash on me, and it seemed like everytime they did crash, it was with something I was working on for a long time and still yet to take a 2 second break to save it. Well I was doing the same thing a little while ago. This was about 30 minutes after creating a new image, and it still wasnt saved. Then, a plugin crashed and I was able to continue working with it. :D

Btw, im not a fan of the photoshop'ish layout, but im sure Ill get used to it. Also, it will make any photoshop work I might do in the future a bit easier.

Share this post


Link to post
Share on other sites

bug found: in motion blur, the left-most pixel in the image ... I want to say it's not being blurred, but it is... it's just... different. The problem is most obvious when using an angle of 90. If your selection does not include the left edge of the image, it doesn't reproduce.

Share this post


Link to post
Share on other sites

Rick,"fix" is absolutely right. But I have to say it will be better if u add some new functions as a Alpha edition.It improved too slowly actually.Thank you for ur hard work whatever.

Share this post


Link to post
Share on other sites
Rick,"fix" is absolutely right. But I have to say it will be better if u add some new functions as a Alpha edition.It improved too slowly actually.Thank you for ur hard work whatever.

Features have to be added slowly. When you add them quickly without extensive testing in between, you get major bugs and deep-rooted problems that you can't diagnose. Paint.NET is advancing in features pretty quickly, considering its size compared to the number of programmers (one). Traditionally, 2.x, 3.x, etc. releases of a program are simply bug fixes and minor improvements; you usually don't see wide, sweeping changes or feature additions until an x.0 release.

Rick is an excellent programmer, though, and bugs are very few and far between.

(Oh, and one more thing: "Alpha" means it's not a final version. So does "Beta" and "Release Candidate." It doesn't mean it's a special version, just an unfinished version.)

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.
Sign in to follow this