Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by S0S

  1. Other than technical issues that I'm not aware of, one way to do it would be to uninstall Paint.NET and .NET framework 1.1 Do a complete uninstall where you use the "Search" feature in the Windows control panel and delete any file still left after the running the uninstaller (it happens). Then go to the "Run" command in the Windows control panel and typing in "Regedit" and going to "Edit" and then "Find" and typing in Paint.NET and .NET framework to get rid of any references to it. After this, click on the installers and start from scratch with a new installation.
  2. That was the one thing that crossed my mind, after I clicked "OK" after the dialog box popped up, if it happens again I'll take a quick snapshot. One other thing I've been noticing and maybe you can give a little more info. on this one but when I copy and paste to a new layer the first time, whatever I have copied pixel wise will show up as a new layer. However, when I do this a second time to form a 3rd layer, nothing shows up. Is there a limit to copying and pasting within new layers? I usually make up about two new ones before flattening down when working on an image. I'll screenshot when I'm working within one and post here if it happens later on. :wink:
  3. Crash log for Paint.NET v2.5 (Release Candidate 2 Release build 2.5.2147.22249) Time of crash: 11/18/2005 5:10:56 AM OS version: 5.1.2600.0 .NET Framework version: 1.1.4322.573 Exception details: System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index at System.Collections.ArrayList.RemoveAt(Int32 index) at PaintDotNet.HistoryStack.StepForward() at PaintDotNet.DocumentWorkspace.historyForm_RedoButtonClicked(Object sender, EventArgs e) at PaintDotNet.HistoryForm.OnRedoButtonClicked() at PaintDotNet.HistoryForm.dotNetToolbar_ButtonClick(Object sender, DotNetToolbarItemClickEventArgs e) at DotNetWidgets.DotNetToolbar.OnMouseUp(MouseEventArgs e) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at DotNetWidgets.DotNetToolbar.WndProc(Message& m) at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ------------------------------------------------------------------------------ Working with a 418 X 252 .jpg and was working on two different layers copying and pasting back and forth trying to get the layering right. I hit the undo button back a few steps and it crashed. Doesn't seem too important but I thought I'd post it anyway.
  4. Nope, it was a compliment. 8) I was also referring to the above post you had made, it was written very straightforward and to the point. .NET v2.0 has already been released?!?! I thought it was still in beta testing? Thanks for the clear-up on that one. :shock: Now for one more quickie question, I have the stand alone installer for .NET v1.1, are you saying that I would have to have .NET v1.1 installed and then install .NET v2.0 as well to make the migration to v2.6? Will v2.6 run on .NET v2.0 by itself without v1.1? I usually do all my Windows updates, ranging from the critical to the optional updates in one session. This splits it down the middle for me, whereas some people may get .NET for Paint.NET, I get it so it's part of my Windows XP and it makes it easier to get Paint.NET and a few other apps. that are taking advantage of the .NET framework.
  5. Very professionally written, Rick. I have a question concerning the .NET framework v2.0, and that is, what will its final filesize be? I remember the .NET framework v1.1 being 24 megs and the security update for it being around 10 megs. How big will .NET v2.0 be when it comes out in December? And obvious update aside, how will the .NET framework v2.0 affect the 32-bit crowd (myself) vs. the 64-bit crowd who use Paint.NET?
  6. To be honest with you, I remember you saying you liked the layout of the Firefox forums, so I thought you had redone the forums to coincide with Beta 5's release. Always full of surprises aren't ya', Rick?
  7. True, it was my initial reaction when I saw the picture though, I thought "there is just an empty space and no extra tool?!" I would just make an arrow with 3 lines, but a custom tool wouldn't be that bad. Also, Neil that happy face idea is crazy ha..ha..good stuff. (Wouldn't that make Paint.NET stand out from the average image editor application :shock: ) I could see the comments on that one...
  8. Ha...ha...this has to be the funniest thing I've seen in a while on these forums. You actually added a tool, but now the toolbar is off and left with a vacant space. The arrow concept is great, but why not just create one using 3 lines? Good tool anyhow.
  9. If Rick and Co. don't mind, I've got the last build of CinePaint before it went under, if anyone wants the source code (to observe) or wants to play/use it, here it is. The GUI is pretty archaic, though.... http://rapidshare.de/files/6467063/Cine ... 7.exe.html
  10. .NET is basically an extension as I understand it that allows "Paint" to be brought to the next level and allows for future applications to have more funtionality and serves "somewhat" as a cross-platform. It's an extra on the XP list, you don't have to have it, but if you want to use Paint.NET, you'll obviously need it. (Thanks to Dan for the link to it, without needing the Windows Update , I didn't have time to look for it)
  11. Wasn't logged in that time, that was me above.
  12. JC, use either the "Magic Wand" tool or the "Lasso" tool to select your area and then switch to the "eraser" tool and erase the background to make your selection transparent beneath. Let me know if you need any more help.
  13. ->Ellipse select, figure out the radius of the ellipse you need and then... ->Crop to Selection This will be in an ellipse, (though you'll have the box on the outside) and you can open and save as a file, or use as a layer.
  14. I have a piece of advice for you, if you are running an XP system and know someone you can trust, have you considered using "Remote Assistance"? It sure would be easier on you, having someone try to look at what is going on with your system and might be able to help you out more in-depth.
  15. That's what I forgot to mention before, will having a 64-bit version of Paint.NET make it easier to work with bits per channel (and larger images in general) than the 32-bit standard we work with now? The performance and memory was something I thought about in hindsight and that would take up more of the system's resources gradually. Yeah, that explanation made enough sense I liken it's algorithm to the compression used in compressing .zip and .rar files but using images instead.
  16. Thanks for the response, I didn't think the "untouchable" Photoshop was only 16-bit. With it's program tailored for digital cameras and scanners, I would think that it would be a little deeper than that in the resolution dept. Anyhow, I still favor Paint.NET's UI over that other one, plain old gray and black boxes just don't have the same "pizazz" that they might have had back in the day. And since most images on the web are only 8-bit, it wouldn't make sense to add any more resolution to them since the images would only be compressed and then transmitted from server to client on the internet.
  17. Rick, How many bits per channel is Paint.NET? I was reading about a new piece of open-source software for images/frame editing called "CinePaint" http://www.cinepaint.movieeditor.com/ (the Windows version is currently unavailable until "Glasgow" is finished) and it boasts an amazing 32-bits per channel! According to the Cinepaint front page: The Gimp is only 8-bits and even Photoshop is only 16-bits. More bits mean more detail and higher resolution, so where does Paint.NET stand? Thanks for answering.
  18. Hmm....that's a bit of an increase. One of the things that I love about Paint.NET is it's simplicity, ease of use and straightforward design. I also love the idea that Paint.NET hasn't exploded into bloatware as I like to keep my system as streamlined as possible. My question is, will Paint.NET be able to stay under the 100,000 mark as far as lines of code go in the future, Rick?
  19. Didn't realize I was logged out when I posted but here I am now. 5" x 4 7/8" in inches was the measurement that I got off of a regular CD cover.
  20. After reading this, I have to say it's one of the brightest and best ways of working with lines on this app. Good idea, Rick. 8)
  21. Root Drive [C] or whatever letter is assigned to the main drive/partition and then WINDOWS/FONTS. That should help you.
  • Create New...