Jump to content

Alph Tech / STUART

Members
  • Content Count

    121
  • Joined

  • Last visited

Everything posted by Alph Tech / STUART

  1. There appears to have been a regression in the bit depth output since the last version. This is what an 8-bit export is looking like: And this is what 32-bit is looking like:
  2. I'd still like to know how this works, since I can't just check the source anymore.
  3. How does Paint.NET composite the layers to the final window canvas? Does it have a persistent bitmap of the image size that it composites to every time there's a change, which is drawn to a double buffer of the window size with the image transformation (zoom/scrolling) which is swapped when drawing is completed or what?
  4. :AddNewLayer: :AddNoise: :AllColorChannels: :AlphaChannel: :AntiAliasingOff: :AntiAliasingOn: << Should these be updated? Why are they even here?
  5. Which icons in Paint.NET came directly from Fugue and which were created/modified by Rick?
  6. This text file was created because Paint.NET crashed. Please e-mail this file to crashlog@getpaint.net so we can diagnose and fix the problem. Hidden Content: Application version: Paint.NET v3.5 (Final Release build 3.50.3596.41598)Time of crash: 11/8.2009 P3:30:09 Application uptime: 00:06:27.3920000 Install directory: C:\Program Files\Paint.NET Current directory: C:\Program Files\Paint.NET OS Version: 6.0.6002.131072 Service Pack 2 Workstation x64 .NET version: CLR 2.0.50727.4200 x64, FX 2.0 2.0SP1 2.0SP2 3.0 3.0SP1 3.0SP2 3.5 3.5SP1 3.5SP1_Client Processor: 2x "AMD Athlon
  7. Tried that, didn't work. Whole log: This text file was created because Paint.NET crashed. Please e-mail this file to crashlog@getpaint.net so we can diagnose and fix the problem. Application version: Paint.NET v3.5 (Final Release build 3.50.3596.41598) Time of crash: 11/7.2009 A4:37:00 Application uptime: 00:00:05.3680000 Install directory: C:\Program Files\Paint.NET Current directory: C:\Program Files\Paint.NET OS Version: 6.0.6002.131072 Service Pack 2 Workstation x64 .NET version: CLR 2.0.50727.4200 x64, FX 2.0 2.0SP1 2.0SP2 3.0 3.0SP1 3.0SP2 3.5 3.5SP1 3.5SP1_Client Processor:
  8. DirectWrite's increased support for grouping font styles isn't being reflected by the menu: ie. if I have several different weights of Helvetica (condensed, extrabold, black, etc), it only displays a menu entry for the standard width.
  9. It's broken. This happens when selecting Curves+ on 3.5 Final. Could be because the package includes version 3.5.3597.39732 instead.
  10. ...Why would a "robot with missiles" be called "Color Reaper"? "Color Reaper" makes sense in the context of the plugin, since it reaps a color from the image. Adding "Grim" as a prefix isn't a particularly descriptive adjective. "Color To Transparency"? I really think this should just replace the current "Chroma Key" plugin, since it does the same operation except with a greater range of inputs.
  11. This is basically just chroma key for any color. Why not call it Chroma Key? "Color to Alpha" was another simple suggestion. Is "Isolate" taken?
  12. Open a new image and delete everything (Select All -> Erase Selection). Now, select all again and transform it with Move Selected Pixels. The transparency in the selection will change from FFFFFF with 0 alpha to 000000 with 0 alpha (use the Color Picker).
  13. Are you saying the error wouldn't reproduce? The JPEG may not be that big, but PDN stores each layer as a 24-bit bitmap. Save the file as a .BMP to see how big it is to PDN, then multiply it by 3 or so. See the topic stickied at the top of the forum, and note history and page file and various other things are backed by HDD.
  14. I posted a new thread on it because the usual response to this bug is "drag somewhere else on the canvas", and I needed to point out that's not always an option, and clarifications like that added as a response after the fact tend to go unnoticed.
  15. Take for example a scenario in which you have 15 different layers, each with certain blending options on that the image is incomprehensible if a few specific layers aren't toggled. (anyone who's played the Clint Howard games like The Fool's Errand knows how this works). If you were to toggle all of those on, it would be a pain to go through and trial and error figure out which ones you had on and off, which is why they have entries in History.
  16. In the same vein as the polygon lasso request, a polygonal accompaniment to the Freeform Shape tool akin to the one in Windows would be excellent.
  17. Currently the only instance of tiling in Paint.NET is in the Rotate/Zoom, which isn't particularly useful unless you want your tiles to be smaller than your current image. What should be included is the option to use tiling to fill the area around the image when expanding the canvas size instead of the secondary color.
  18. It would be nice if toggling a layer's visibility on and off repeatedly only did and undid one Layer Visibility Properties item in History instead of flooding the History window with a bunch of Layer Visibility Properties representing the repeated toggling and untoggling of the layer.
  19. Wouldn't it make sense to capitalize the .NET in the paint.net wordmark to embrace the new .NET logo/rebranding?
  20. If you zoom in on a selection of a certain size and your window isn't big enough it's impossible to move the selection because the hotspot area around the nubs is inflated with the zoom where it shouldn't be. (I'm aware you can drag anywhere on the visible canvas area. Sometimes the inflated selection handles will take occupy the entire visible canvas area.)
×
×
  • Create New...