NeoSpearBlade

Since v.4.0.10 came out, some people have reported issues with the Zoom tool and commands. Rick has confirmed that it's a bug and it'll (hopefully) will be fixed in the next update (v.4.0.11?). So what's going on? I'll explain here and show a simple workaround until it's fixed. From what I've read, the problem is with the Zoom function and how it works. The bug only happens when the Zoom type is Normal (), not Windowed (). I'm not sure if this means anything or if it's even relevant. Also, it doesn't matter what version of Windows you're using, the bug is still present. When zooming in or out using the Zoom Tool (), the metaphorically invisible center of the canvas gets moved to where the cursor was clicked on, the zoom is applied and then it repositions the 'camera' to focus on the new center point. However, while zooming in or out using the menu, status bar, mouse wheel or keyboard shortcuts ()() do the same thing, it doesn't reposition the 'camera'. Now, the workaround for this bug is simple. Just make sure the mouse is NOT inside the canvas when zooming. It doesn't matter where the mouse is, as long as it's not inside the canvas, the Zoom function will work correctly. If you need to recenter the canvas, just press Ctrl+B twice. I hope this was somewhat informative.

Yep, I knew I forgot to mention something. *sigh* Just when I was about to edit the original post again..... I didn't launch the update from the USB, nor did I installed it fresh into the USB. I installed it normally then I copied the folder onto the USB device. After fixing an issue with it, it works just fine from the USB, although it runs a little bit slower, which I expected. Before the update, I copy-pasted the folder back into a computer' desktop then launched the update from the PC's hard drive, not from the USB device. I hope that clears things up. Does that help at all?

Confusing title, I know. Allow me to explain. I have Paint.NET installed in an external USB device to make it portable and I just updated it to v.4.0.10 using the program's internal update checker/installer. After the update was complete, I launched it to see what's new.....except I launched v.4.0.5, the previous version I had. So where did the new version go to? As it turns out, the update process installs where Paint.NET is set by default, inside the PC's program folder, not in the folder where the program was launched from. Is this normal behavior? It doesn't seem like it is. Considering the update installer didn't ask me where to install it, I though it would replace the files where the program was launched from, which sounds perfectly reasonable, like common sense. On a related side note, I downloaded Paint.NET's full installer as well in case the update process didn't work correctly. While the full installer is for brand new installs (obviously), it's annoying that I have to go through the initial installation settings when I want to use this as a manual update. Is it possible to have a 3rd option at the start of the installation where it functions as an update to a previous existing version? And can I tell it where the previous version is located so it can then update/replace those files?

The topic's been moved to Troubleshooting so I guess the plugin was not involved. OK, glad to know that. I can't exactly do that on university computers without someone raising an eyebrow about how often I ask for the password to log in to the computer after purposefully crashing it. (Campus policy; students should not know the computer login password.) Additionally, while my laptop isn't systematically fragile, I'm being more gentle on it the longer it lives since my old laptop died by attempting to run a software that was too powerful to handle so that's not an option as well. Long story short, I don't have the the opportunities to do this, nor do I have the will. I get a minor panic attack when a computer I'm using suddenly freezes, intentional or not. Past nightmarish experiences did that to me and I don't wish to repeat it anytime soon. So, it's uncommon in that not many people report it therefore it's not high up in priorities. OK, I understand that. But, the possible end result by encountering it is A COMPLETE TOTAL SYSTEM FREEZE. Unexpected things can happen when you get a system freeze when you don't expect it, especially if you had something important running in the background or were using it along with Paint.NET. God forbid you weren't currently saving or rendering something when the freeze happened. I got off lucky as while I had something important running when I froze, I did a coincidental save to that project just prior to the freeze. With all that said, I still understand why it isn't a top priority and I won't be mean to you because of that. After all, you have other things to do other than working on Paint.NET, right? However, the other Paint.NET users and newcomers should at least know that this is a possibility that can happen to them. Is this listed in the current v.4.0.10 bug list?

This is a bug/error/crash/whatever but the troubleshooting section is not for problems with plugins involved. I'm unsure if the plugin was involved at all to begin with but I decided to put it here. Well, this is an odd one and it's the first time this happened to me. First, the stats. OS: Windows 7 Paint.NET Version: 4.0.5 Now, I was unaware that v.4.0.10 came out earlier this month when I got this error. That said, it might still be present in the new version. So, what happened? Well, I went to the options screen to change my default settings when I noticed a new tab labeled Plugin Errors. I was not expecting this but I did install some new plugins yesterday. So I open it and the error is for CurtisBlack.Common.dll from Curtis' Plugin Pack. I click on it and it gave me some stats about the error that I didn't understand so I decided to remove that plugin just to be safe. Only one problem. The entire PC froze/locked me out after the error information was shown. Anything that was working or animating in the background froze as well. The only thing I could do was move around the mouse but eventually that froze as well. Needless to say, it didn't generate a pdncrash.log file. Also, I was not using my laptop PC. I was using a university PC with software installed and configured for game design and creation classes (Unreal, Maya, VS Express, ZBrush, etc.) so this isn't a weak PC although it's definitely more powerful than my 8-year-old laptop. I'm not sure if this info is relevant, though. Has this happened to anyone else? Additionally, I'm not exactly motivated to try to replicate this crash on multiple PCs so can anyone verify this happening as well? Regardless, one of my lingering issues with this is, was the problem with the specified plugin or the Plugin Error tab itself? For the moment, I removed all recently-added plugins from the software.

So plugins can't change those values but they are still readable apparently. I've been using Paint.Net for a long time (since v3.20). That said, I'm mostly unaware what happens within the program. That's why I'm initially thinking that this shouldn't be a problem, just open a dialog window with a similar layout as Canvas Size to do the changes. Then again, I don't know how Paint.Net actually works, I just know how to use it. I'm aware of that (I did say arrow keys) but with the images I'm working with ever expanding in canvas size, even that's not fast enough. Maybe add a Ctrl+Shift+arrow keys for 100 pixels at a time? Um, I want to move the selection, not flip it. Sure, it sounds fast but then I have to unflip it, which takes time and this feels like an unnecessary step.

I noticed that when a selection is present, the bottom-left corner of Paint.Net tells me the info of the selection box which looks like this: Selection top left: 111, 31. Bounding rectangle size: 153 x 150. Area: 22,950 pixels square I mention this because I've been using a combination of the Rectangle Select, Magic Wand and Move Selection tools a lot lately and I feel that there's gotta be a way for this to go faster. So is there a way (either built-in or with a plugin) to quickly/instantly move and/or resize the selection box, regardless if you're using or ? For example, I have a selection I created on one side of the image (Selection top left: 512, 36) but I now want to move it all the way to the other side and since I know exactly where I want it to go because I already know the coordinates of the location (Selection top left: 3936, 36), I can do (whatever the solution is) to do it very quickly instead of using the mouse or the arrow keys to move it. So, is this possible at the moment (built-in/plugin-wise) or is this something that can be done in the future?

Hey, sorry for the VERY late reply. ^_^' I checked that plugin you mentioned. It doesn't do what I described above, it does exactly what the title says, animates a sprite sheet. Might be useful in the future but it's not what I'm looking for. So, I guess I have to wait until either someone creates a plugin with the effect that I explained above or I make it myself and both ain't gonna happen anytime soon. *sigh*

Hmm..... I don't know the name of what I'm looking for..... Um, I need some help. I'm not sure if I can ask this here so I apologize in advance. I'm looking for a plugin that helps me in sprite editing.....OK, not specifically sprite-based but it's similar. The thing I'm looking for is something specific so I'll try my best to explain it. I have this image sheet I'm working on (see here). Each image is in the same spot inside a 32x32 square and each one has a different color for each image on the same row. Now, here's what I'm looking for. Let's say that after I finished applying the colors, I noticed an error in pixel placements for one of the images. To fix the error, I have to either: Fix the base image, copy-paste the base over the old images and reapply the colors. OR Go to each and every image on the same row to apply the fix. Both take quite a bit of time to do, especially in the future as I'm planning to do more than 80 different colors. The plugin I want is something that allows me to select one or more pixels on the base image and the plugin automatically selects the same pixels on the same row as the base image. So for example, if I select the pixel located at [7,14] in a 32x32 square, the plugin (after being told the base dimensions) selects the pixels at [39,14], [71,14], [103,14] and so on until the end of the row. Having something like this will really help me cut down on the time spent editing. So, does one of the plugins in this index already do that or not?