A_Pickle

Well, I'm still using Paint.NET. I know I haven't been active in these forums for awhile, but I still use the golden program and even surf the topics every so often. Today, I was using the program to make a little computer teaching guide for my computer inept parents, using Microsoft Word 2007 and Paint.NET. To my delight, I saw that Paint.NET wanted to update to version 3.35. As is customary for me whenever Paint.NET requests an update, I click the "More info" link to the Paint.NET changelog/roadmap and read all about the new bells and whistles, changes and fixes... and I thought to myself just how much attention to detail and professionalism this development team manifests. Seriously, plus and minus signs next to the cursors? It's not a biggie -- but it helps. I can't tell you how many times I wish there was some kind of onscreen indicator that I was holding down the proper key for the action I wanted, and now there is one. And then all of the fixes, including the no longer ultra-laggy selection box... I mean, that's icing on the cake. I've been waiting for that one like I'd been waiting for a good ATI graphics card -- and my waiting has panned out for the latter, so I can only assume that it will for the former. You guys are awesome, and I just wanted to say thanks for making the best image editor on the planet. Thanks for making it trim and fast, thanks for making it have the best interface ever, and thanks for making it the GIMP killer it is. I don't know if I've donated to the cause before, but as soon as I can, I certainly will. Keep 'em coming, guys.

As I'm sure most do, I find feature requests as I'm using Paint.NET -- when I have to do something that takes far more steps than it should. And today, I needed a rounded rectangle, but as I was using it for an image at 1920x1080 pixels, I found that the corners were too sharp. It would've been nice to have a way to edit the radius length that generates the corner arcs.

Thanks Rick. v3.20 is awesome... so awesome, in fact, it deserves it's own thread in honor to it. You guys are an excellent development team, providing us, your userbase, with a fantastically-designed and well-supported application. v3.20 came out... and it was awesome... and we already have a v3.22 in beta. I don't know of any other piece of software withe developers quite so willing and able to fix bugs and deliver new features as quickly. You guys had a 256x256 pixel icon BEFORE Windows Vista was launched, and it's fully compatible with or without UAC, with or without administrator rights. I just don't even know what to say other than thank you, and keep it up. You guys rule. New Paint.NET features and fixes are like... the highlight of my day. Because I'm a geek. PS: Incidentally, if you have a laptop with ATI Radeon graphics, and you'd like to update your graphics drivers, I may have something that might make your day too. Figured I should mention that for whatever reason.

I was working with some inordinately large images, but I figured I should post my pdncrash.log file here for you guys to look at. :3 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: 11/22/2007 7:38:26 AM Application uptime: 00:14:59.9241184 OS Version: 6.0.6000.0 Workstation x86 .NET Framework version: 2.0.50727.312 x86 Processor: 2x "Intel(R) Core(TM)2 CPU T7400 @ 2.16GHz" @ ~2161MHz (DEP, SSE, SSE2, SSE3) Physical memory: 2045 MB Tablet PC: no Locale: pdnr.c: en-US, hklm: en-US, hkcu: n/a, cc: en-US, cuic: en-US Exception details: System.OutOfMemoryException: CreateDIBSection returned NULL (8) while attempting to allocate 5000x7000 bitmap at PaintDotNet.SystemLayer.Memory.AllocateBitmap(Int32 width, Int32 height, IntPtr& handle) at PaintDotNet.MemoryBlock.Allocate(Int32 width, Int32 height, IntPtr& handle, Boolean allowRetry) at PaintDotNet.MemoryBlock.Allocate(Int32 width, Int32 height, IntPtr& handle, Boolean allowRetry) at PaintDotNet.MemoryBlock..ctor(Int32 width, Int32 height) at PaintDotNet.Surface..ctor(Int32 width, Int32 height) at PaintDotNet.Surface..ctor(Size size) at PaintDotNet.DocumentWorkspace.OnDocumentChanged() at PaintDotNet.DocumentView.DocumentSetImpl(Document value) at PaintDotNet.DocumentView.set_Document(Document value) at PaintDotNet.DocumentWorkspace.PaintDotNet.IHistoryWorkspace.set_Document(Document ) at PaintDotNet.HistoryMementos.ReplaceDocumentHistoryMemento.OnUndo() at PaintDotNet.HistoryMemento.PerformUndo() at PaintDotNet.HistoryMementos.CompoundHistoryMemento.OnUndo() at PaintDotNet.HistoryMemento.PerformUndo() at PaintDotNet.HistoryStack.StepBackwardImpl() at PaintDotNet.HistoryStack.StepBackward() at PaintDotNet.Actions.HistoryUndoAction.PerformAction(DocumentWorkspace documentWorkspace) at PaintDotNet.DocumentWorkspace.PerformAction(DocumentWorkspaceAction action) at PaintDotNet.Menus.EditMenu.MenuEditUndo_Click(Object sender, EventArgs e) at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e) at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e) at PaintDotNet.PdnMenuItem.OnClick(EventArgs e) at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e) at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met) at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met) at System.Windows.Forms.ToolStripItem.PerformClick() at PaintDotNet.PdnMenuItem.OnShortcutKeyPressed(Keys keys) at PaintDotNet.PdnBaseForm.ProcessFormHotKey(Keys keyData) at PaintDotNet.PdnBaseForm.ProcessCmdKeyData(Keys keyData) at PaintDotNet.PdnBaseForm.ProcessCmdKey(Message& msg, Keys keyData) at System.Windows.Forms.Control.ProcessCmdKey(Message& msg, Keys keyData) at System.Windows.Forms.ContainerControl.ProcessCmdKey(Message& msg, Keys keyData) at System.Windows.Forms.Control.ProcessCmdKey(Message& msg, Keys keyData) at System.Windows.Forms.Control.ProcessCmdKey(Message& msg, Keys keyData) at System.Windows.Forms.ContainerControl.ProcessCmdKey(Message& msg, Keys keyData) at PaintDotNet.DocumentView.ProcessCmdKey(Message& msg, Keys keyData) at System.Windows.Forms.Control.ProcessCmdKey(Message& msg, Keys keyData) at System.Windows.Forms.Control.PreProcessMessage(Message& msg) at System.Windows.Forms.Control.PreProcessControlMessageInternal(Control target, Message& msg) at System.Windows.Forms.Application.ThreadContext.PreTranslateMessage(MSG& msg) ------------------------------------------------------------------------------ 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: 11/22/2007 7:42:36 AM Application uptime: 00:00:44.7224718 OS Version: 6.0.6000.0 Workstation x86 .NET Framework version: 2.0.50727.312 x86 Processor: 2x "Intel(R) Core(TM)2 CPU T7400 @ 2.16GHz" @ ~2161MHz (DEP, SSE, SSE2, SSE3) Physical memory: 2045 MB Tablet PC: no Locale: pdnr.c: en-US, hklm: en-US, hkcu: n/a, cc: en-US, cuic: en-US Exception details: System.OutOfMemoryException: CreateDIBSection returned NULL (8) while attempting to allocate 5000x7000 bitmap at PaintDotNet.SystemLayer.Memory.AllocateBitmap(Int32 width, Int32 height, IntPtr& handle) at PaintDotNet.MemoryBlock.Allocate(Int32 width, Int32 height, IntPtr& handle, Boolean allowRetry) at PaintDotNet.MemoryBlock.Allocate(Int32 width, Int32 height, IntPtr& handle, Boolean allowRetry) at PaintDotNet.MemoryBlock..ctor(Int32 width, Int32 height) at PaintDotNet.Surface..ctor(Int32 width, Int32 height) at PaintDotNet.Surface..ctor(Size size) at PaintDotNet.DocumentWorkspace.OnDocumentChanged() at PaintDotNet.DocumentView.DocumentSetImpl(Document value) at PaintDotNet.DocumentView.set_Document(Document value) at PaintDotNet.Actions.ImportFromFileAction.DoCanvasResize(DocumentWorkspace documentWorkspace, Size newLayerSize) at PaintDotNet.Actions.ImportFromFileAction.ImportOneLayer(DocumentWorkspace documentWorkspace, BitmapLayer layer) at PaintDotNet.Actions.ImportFromFileAction.ImportDocument(DocumentWorkspace documentWorkspace, Document document, Rectangle& lastLayerBounds) at PaintDotNet.Actions.ImportFromFileAction.ImportOneFile(DocumentWorkspace documentWorkspace, String fileName, Rectangle& lastLayerBounds) at PaintDotNet.Actions.ImportFromFileAction.ImportMultipleFiles(DocumentWorkspace documentWorkspace, String[] fileNames) at PaintDotNet.Actions.ImportFromFileAction.PerformAction(DocumentWorkspace documentWorkspace) at PaintDotNet.DocumentWorkspace.PerformAction(DocumentWorkspaceAction action) at PaintDotNet.Menus.LayersMenu.MenuLayersImportFromFile_Click(Object sender, EventArgs e) at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e) at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e) at PaintDotNet.PdnMenuItem.OnClick(EventArgs e) at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e) at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e) at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met) at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met) at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea) at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ScrollableControl.WndProc(Message& m) at System.Windows.Forms.ToolStrip.WndProc(Message& m) at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ------------------------------------------------------------------------------

Kick < no swearing >! This is one hell of an update Rick, thanks! EDIT: I found a sorta-kinda bug. Is it just me, or is the scrollbar in this plugin properties box... erm... unnecessary?

Sorry, Rick. And no, the standard Windows Firewall (WF) and Windows Firewall with Advanced Security (WFWAS) are quite different. I'm pretty sure the WFWAS implicitly denies anything that isn't explicitly permitted in the rule list. It doesn't just have an "Exceptions" tab. It's definitely blocking it -- but now that I know the specific .exe that it uses -- I can let it through. Thanks!

More than meets the eye!

Not really. I need to know the specific executable that handles Paint.NET updating -- because the firewall I'm using (Windows Firewall with Advanced Security -- there's a difference between that and just plain Windows Firewall) doesn't prompt me when a program tries to access the internet. So I need to know the executable that tries to access -- so that I can create a rule that will permit it through every time -- rather than having to turn my firewall on and off every time (it's an annoyingly slow firewall). Incidentally, does anyone know how to reset the firewall?

See, I'm kind of an idiot, and I started using the Windows Firewall with Advanced Security in Windows Vista. Great firewall, I'm really impressed with it and happy that Microsoft has bundled a really flexible and powerful firewall with their operating system. It was a long time coming. Great firewall, don't get me wrong. But I'm somewhat stuck now. I really don't know how to... uh... stop using that firewall (so if anyone could help me in that respect, that'd be great). Anyways, I need to create a rule to allow Paint.NET to update so that I don't have to deactivate my firewall to do it. What executable is responsible for Paint.NET update.

I used to be around here a lot more, but I still use Paint.NET as my primary photo/image editing application. As such, whenever I come across an interface/functionality hurdle, I think of a much better way to do it. Sadly, I don't know how to code... so I can't really submit it in code itself.

I think it'd be beneficial if Paint.NET had a good grid overlay, with options to set primary grid line spacing to user-specified sizes, and maybe to have user-specified subdivision levels and all of that with snapping. This'd be amazing. Are my feature requests annoying?

NICE. GIMP, thy doom draws nigh! I'm liking the monthly update plan, and arrowheads look fantastic. Clever "not-saved" feature, too. I like that. As for the no more help file... I dunno man. ~4 MB isn't that big of a file, particularly with the widespread availability of broadband connections. Also, the .NET Framework 2.0 isn't even a "recommended update" via Windows Update in XP -- it's an optional one. That makes ordinary people have to WORK at getting .NET Framework 2.0, and... I dunno. I really haven't been impressed with people's ability to navigate through a computer or programs... ...Just my thoughts. I honestly don't know why the .NET Framwork isn't just installed as a critical update. So many programs are dependent on it...

Rick, just a question... ...I was Wikipedia-ing on Mac OS X 10.5 Leopard, and found my way all the way over in the Windows Presentation Foundation. .NET 3.0... apparently... supports resolution independence. Is this something we'll see in Paint.NET when it adopts the .NET Framework 3.0?

Now that Vista has horizontal scrolling support built-in, couldn't Paint.NET support tilt-wheels?

And I'm pretty sure it's not in the thread, 'cuz I've read it and re-read it just for verification before I posted this. Anyways, wouldn't it be damn cool if we could have a few more options for circular and rectangular selection? Like... the ability to set an aspect ratio for a rectangular selection box, or to be able to create one with preset pixel dimensions? Yeah, that'd be sweet. Totally myphotoshop idea.

I found a bug in the setup of Paint.NET. I can be your official 120 DPI bug tester.

Hey, Rick, are there any plans to introduce subpixel selection (like Photoshop's) in Paint.NET? So as to anti-alias selected objects? Eh?

You can set colors to be transparent. In the Color palette, hit "More >>" and, at the bottom right-hand corner, there's a slider labelled "Transparency - Alpha." If you drag the slider all the way to the left, or set the value to "0," then you can draw transparent pixels.

I was just playing around in Paint.NET today, and decided to set a project for myself. I went over to Userbars.org, and I couldn't help but notice that there was no "Dell E1705 User" userbar. So I made one, as an homage to a very, VERY, cool notebook. EDIT: Gah! I forgot the black outline on my original userbar. Here's the revamped one.

I, for one, believe that, while the Rotate/Zoom command is innovative, it isn't quite "wysiwyg" enough. Something similar to Photoshop's transform methods (distort, skew, rotate, size, and perspective) would be fantastic! Rick, do you have various image-editing applications on hand for comparison?

Fnord?

The number of buttons in an application is directly proportional to it's professional look rating.

Kinda blurry, as though they've been stretched to match my DPI settings.

Cool. Thanks, Rick. Apart from that color palette bug, I haven't seen anything odd happen at 120 DPI. The icons on the palettes have that "non-native" look about them, but otherwise... we're gravy. Paint.NET 3 is looking to be awesome, Rick.

Sweet jesus, this whole thing is FANTASTIC. Any love for us 120 DPI-ers?