Jump to content

Bruce Bowyer-Smyth

  • Posts

  • Joined

  • Last visited

Profile Information

  • Gender
    Not Telling
  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Bruce Bowyer-Smyth's Achievements


Collaborator (7/14)

  • First Post
  • Collaborator
  • Conversation Starter
  • Week One Done
  • One Month Later

Recent Badges



  1. I can't find the difference between the old and the new just by reading the decompile. dotPeek does the pointer code correctly if someone is keen.
  2. @Rick Brewster Do desktop apps support the execution alias? https://docs.microsoft.com/en-us/uwp/schemas/appxpackage/uapmanifestschema/element-uap5-executionalias
  3. Nice surprise on a professional game developer's PC at DoubleFine. The Making of Grim Fandango Remastered: Episode 2 http://youtu.be/s-LSMCYjHow at 5:45
  4. 3.5 gets the correct size. Sent you the files by forum message.
  5. Copying a 200x63 image from Word 2013 to paste into Paint.net and it thinks it is 313x98. MS Paint is picking up the correct size.
  6. Added Paint.net v4 compatible download. I'll leave the old version available for a while until v4 is public. Switched to using SharpDX for the GPU code. Gausian blur 17% faster. Some other minor performance improvements.
  7. I have an update to my Blur Pack (http://forums.getpaint.net/index.php?/topic/19364-hardware-accelerated-blur-pack-v24/) targeting paint.net 4. Thought that I would put it out for a bit of a test first seeing that I have switched over to using SharpDX and made some other performance improvements. Download here -> http://www.wmf2wpf.com/downloads/hablurpack3.zip If there are no issues I'll add it to the other post for general download. Thanks
  8. At some zoom levels blocking will appear with noise. Can you see them at 100% zoom?
  9. It's a weird one. Doing some more testing it only seems to happen during the effect preview. So the codelab script is working fine. Using the basic effect below, put a breakpoint on the line indicated with a condition of "rect.Right == dst.Width" Using an 800x600 the breakpoint is hit during preview and after clicking ok to commit. Opening a 4800x6400 the first rect in the preview is {X=0,Y=0,Width=4798,Height=1} and the breakpoint is never hit during the preview. Click OK and the first rect is {X=4798,Y=0,Width=2,Height=1} and the break point is hit. The preview seems to be missing the width of 2 rects. If you zoom right in on the right hand edge of the image the breakpoint IS hit during the preview. It does seem to be related to zoom levels. If I zoom out 2 times it starts working. This screen size is 1280x1024 and image as opened at zoom level "Window". using PaintDotNet; using PaintDotNet.Effects; using PaintDotNet.PropertySystem; using System.Collections.Generic; using System.Drawing; namespace ClassLibrary1 { [PluginSupportInfo(typeof(PluginSupportInfo), DisplayName = "Width Test")] public class Class1 : PaintDotNet.Effects.PropertyBasedEffect { public static string StaticName { get { return "Width Test"; } } public static Bitmap StaticIcon { get { return new Bitmap(16, 16); } } public Class1() : base(Class1.StaticName, Class1.StaticIcon, SubmenuNames.Blurs, PaintDotNet.Effects.EffectFlags.Configurable | PaintDotNet.Effects.EffectFlags.SingleThreaded) { } protected override void OnRender(Rectangle[] rois, int startIndex, int length) { var dst = base.DstArgs.Surface; foreach (Rectangle rect in rois) { // Breakpoint next line for (int y = rect.Top; y < rect.Bottom; y++) { for (int x = rect.Left; x < rect.Right; x++) { dst[x, y] = ColorBgra.Red; } } } } protected override PropertyCollection OnCreatePropertyCollection() { List<Property> props = new List<Property>(); return new PropertyCollection(props); } } }
  10. No sorry there is still an issue. Rectangle.Right is defined as "The value of the Right property represents the x-coordinate of the first point at the right edge of the rectangle that is not contained in the rectangle". So Right will equal Width when Left = 0. At some point Paint.NET is passing in Rectangles that do not reach the width as in the 4800 to 4798 above. There are also no additional rois passed in that will cover the gap in the width. Mentioned above I was sure this didn't used to be a problem on my old Win7 box.
  11. You are right. It is the small sizes that were the problem. It appears to be known issue with the Rectangle struct. var r = new Rectangle(0, 0, 100, 10); Gives r.Right = 100 and r.Bottom = 10 when they should be 99 and 9. Nothing wrong with Paint.NET, cheers.
  12. Didn't assume it. Only used it for testing. With a full image selected I never received a roi that went to the edge.
  13. Just using the startIndex and length that are passed in. Even so there is never more than one Rectangle at a time. On the larger images this is never true: roi.Right == base.SrcArgs.Width. Which it is with the smaller images.
  14. This is just the Rectange[] rois passed into the Render. I was pretty sure this used to work when I was on Win7. Possible problem under Win8.
  • Create New...