• Content Count

  • Joined

  • Last visited

Posts posted by alexo

  1. 2 hours ago, toe_head2001 said:

    That's not an accurate/reliable way to track plugin updates. There are plenty of reasons to edit a post besides uploading a new plugin version. For example, fixing broken links and images, fixing typos, ect.


    That is correct of course, and it's the reason I said "may have" above.  It could serve as a flag to look at the post, since the process is manual.  A diff from the previous version would make it easier to distinguish between an actual update and fix.  Still not a good solution but it could work.


    A better approach would be to look for a distinctive pattern within the message body (Such as "~~version=" for example) and let plugin authors know that if they include it and keep it updated, an automated system could track the versioning.  The ones that want to take advantage of the feature will do it.


  2. Thank you for the explanation, EER.


    I'm just going to brainstorm a little...


    I assume (and please correct me if I am wrong) that the plugin uses the data from the plugin index, which tracks the posts in the forum, either automatically or manually.

    The most effective way of doing it IMHO would be to scrape the data directly from the DB.  Even if some manual massaging would be needed, it would still be a good starting point.

    I do not have access to the Invision DB schema so I cannot say whether it tracks the modification time of edited posts, but I know that most (all?) other BBS systems do, and if that information is available, then it could indicate that a new version may have become available.

    Just a thought.

  3. Getting errors when using lasso selected regions:

    File: C:\Program Files\\Effects\ContentAwareFill.dll
          Name: ContentAwareFill.ContentAwareFillEffect
          Author: null54
          Copyright: Copyright © 2018 Nicholas Hayes (aka null54)
          Full error message: PaintDotNet.WorkerThreadException: Worker thread threw an exception ---> System.NullReferenceException: Object reference not set to an instance of an object.
       at ContentAwareFill.ContentAwareFillEffect.OnConfigDialogProgress(Int32 value)
       at ContentAwareFill.Resynthesizer.Synthesize(Int32 pass, Func`1 abortCallback)
       at ContentAwareFill.Resynthesizer.ContentAwareFill(Func`1 abortCallback)
       at ContentAwareFill.ContentAwareFillEffect.OnSetRenderInfo(EffectConfigToken parameters, RenderArgs dstArgs, RenderArgs srcArgs)
       at PaintDotNet.Effects.BackgroundEffectRenderer.ThreadFunction() in D:\src\pdn\src\PaintDotNet\Effects\BackgroundEffectRenderer.cs:line 225
       --- End of inner exception stack trace ---
       at PaintDotNet.Effects.BackgroundEffectRenderer.DrainExceptions() in D:\src\pdn\src\PaintDotNet\Effects\BackgroundEffectRenderer.cs:line 418
       at PaintDotNet.Effects.BackgroundEffectRenderer.Abort() in D:\src\pdn\src\PaintDotNet\Effects\BackgroundEffectRenderer.cs:line 374
       at PaintDotNet.Effects.BackgroundEffectRenderer.Start() in D:\src\pdn\src\PaintDotNet\Effects\BackgroundEffectRenderer.cs:line 320
       at PaintDotNet.Menus.EffectMenuBase.<>c__DisplayClass42_5.<RunEffectImpl>b__5() in D:\src\pdn\src\PaintDotNet\Menus\EffectMenuBase.cs:line 1032


  4. 18 hours ago, null54 said:


    The effect renders automatically because that is the expected behavior for all Paint.NET effects that do not show their own drawing surface.

    If I were to add an apply button it would be controlled by a checkbox that disables the automatic rendering.


    The problem is that if I want to move the slider from the default 50 to say 12, the process starts as soon as I start moving the slider, before it reaches the mark.  Then I have to wait for it to finish (can take 20 second's or so),  then try to trigger it again, which is problem when the slider is already in the correct position, so I end up running it twice more.  It is an unnecessary inconvenience.


  5. OK, figured out how to do it manually


    Start with layer #1: the wood texture background

    Add layer #2: a copy of #1

    Add layer #3: The text.  Black color, anti-aliasing off

    Select text using magic wand, global, zero % tolerance

    Switch to layer #2 and delete selection

    Delete layer #3

    Add new layer #3: a copy of layer #2

    Select cut out text as above, then invert selection

    Feather selection, 1 pixel, preserve edges

    Switch to layer #2, use Hue/Saturation to set lightness to zero

    Reduce layer opacity (I used 50)

    Switch to layer #1 and use Hue/Saturation to lighten it up (I used 30)



    Thanks for your help!

  6. Thank you for your reply, but it didn't work for me.


    This tutorial creates a nice textile weave pattern:


    Unfortunately, when I tried using it on black text, the result looked nothing like I need.




    I already have the background and only need the foreground text.


    Thank you.

  7. I just installed 3.5.7, and now I'm having trouble with the copy command (both CTRL+C and Edit->Copy). The error I'm getting is "There was an error copying the image to the clipboard". This was working in the previous version I had installed (3.5.6). I think it might be related to the number of pixels selected. 2520x2848 produces this error, whereas 2377x2395 doesn't produce the error.

    I'm running Win XP Pro 32-bit with 4gigs of ram on a quadcore processor (Q6600), so I should hope it's not running out of memory.

    I started having this problem in 3.5.10. It would not copy images larger than about 400K pixels, which is really quite small

    Windows paint has no problems with images even larger than that.

    Any ideas? I can't work... :(