Jump to content

Rick Brewster

  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Rick Brewster

  1. ncmike1, Not all cameras or scanners will work. They must have support for WIA (Windows Image Acquisition), and you must be running Windows XP SP1 or Windows Server 2003.
  2. I've filed a suggestion bug on this. We'll see what Tom thinks -- he wrote Levels.
  3. We hear ya. Version 2.2 is going to have a completely rewritten selection system that will do everything you want, and probably more. We haven't had it yet because it's a difficult problem to both design well and implement in a performant manner. But we're getting there.
  4. Yes. v2.2 is going to be released in both English and German.
  5. Makes sense ... I've filed a bug. You'll see it in v2.2.
  6. Most likely you are opening a low-color or monochrome TIFF. Paint.NET only works with 32-bit color, so when you open a low-color or monochrome TIFF the pixels are scaled up to 32-bit. Then when you save, the file size reflects this.
  7. Luckily we keep a private archive of all released builds. I've copied it to our web server so you can download it: http://www.eecs.wsu.edu/paint.net/files ... t_2_1a.zip
  8. The events in Tool.cs do not call event delegates for external clients to handle -- they are meant to be overriden by derived classes. What will happen is that SurfaceBox or DocumentView will receive input, possibly via OnMouseDown or the stylus input plugin, and will then raise a corresponding event that is handled by DocumentWorkspace. This input event is then pushed to the current Tool via the Perform* methods. If you want to know how it works, you really should just use the excellent debugging facilities provided by Visual Studio and step through the code. Set a breakpoint where you want
  9. You might find it useful to select the area you want to smear/blur, and then use the Blur or Motion Blur effect to smear that area.
  10. Yes, Windows XP SP1 is required for this functionality ... we wouldn't make a dialog box that lies to you, after all.
  11. The eraser is meant to set an area to be transparent (alpha channel equal to zero) -- if you are working with multiple layers the way we do this makes much more sense than the way it works with just 1 layer. They can always just use the paintbrush to draw with white. The way things are set up when you start the application, you can basically use the left mouse button to draw with black, and then the right mouse button will 'erase' with white because that is the default secondary ("background") color.
  12. That's not quite how it works. If only it were that simple PaintDotNet.Data.dll is where all the document related code resides. That doesn't mean it can be plugged in to other programs. However, those other programs could write their own adapter code that used PaintDotNet.Data.dll to load .PDN files.
  13. Try http://moab.eecs.wsu.edu/paint.net/ while I bug the guys at WSU to get the main, normal URL back up ...
  14. There is no effect that does this, but you can accomplish this yourself quite easily: 1. Desaturate the layer you want to change to another color. 2. Create a new layer on top of it. 3. Set that layer to use the Multiply blending mode. 4. Fill the layer with the color you are interested in.
  15. We are well aware of how it works, no need to explain it. I disagree that it is counter-intuitive. People who will be working with transparency are generally at the higher end of our user base and will recognize what is going on and how to accomplish what they want. Imagine if it worked the way you think it should. There would be no way to move pixels around in an overwriting fashion. Everything would always be blended, new layer or not. With our current design you just make a new layer, move the pixels to the new layer, and then move it around. We are functionally complete.
  16. We are adding this type of status text to v2.2.
  17. Sorry, Paint.NET is not an "open door" project. We keep the number of people working on it small to maintain manageability and code quality.
  18. Are you by any chance using Large Fonts or high-dpi (120dpi) settings in Windows?
  19. Dan is correct. This is not a bug. When you move the pixels around we are copying them verbatim, so to speak. We are not blending them in to the existing pixels on that layer.
  20. Do you mean resizing in Paint.NET through the Image -> Resize menu option? You can use "Nearest Neighbor" resampling to achieve the pixelated look. Or do you mean in your C# code and using Graphics.DrawImage? If so set the Graphics.InterpolationMode to InterpolationMode.NearestNeighbor.
  21. Read the sticky in this section of the forum BEFORE you post.
  22. This is due to Paint.NET's architecture with respect to how it allocates and uses surfaces (bitmaps) in combination with memory address space limitations with a 32-bit OS. It's comes down to a tradeoff between performance, memory usage, and development time. Right now we have good performance, high memory usage, and low development time. We won't be fixing this. Instead, we'll be relying on the trend towards 64-bit CPU's and OS' (Windows XP x64 and Vista) to remove this barrier. We will have a 64-bit version of Paint.NET sometime soon after both Visual Studio 2005 and .NET Framework 2.0 ship.
  • Create New...