Jump to content

tunedude

Members
  • Posts

    28
  • Joined

  • Last visited

Posts posted by tunedude

  1. That might be an interesting effect, but AFAIK not at all the same as explained in the link you sent.

    The reason, the formula described is a Transfer function and should thus be applied to the frequency domain (sorry if I get the terminology wrong, it's a while since I did my signal processing course..). That is you should do a FFT, apply the function, then do an IFFT, and not apply it directly to pixel values.

  2. This is a long shot, but the symptoms are similar if you haven't installed the appropriate VC++ runtime

    http://www.microsoft.com/downloads/details.aspx?familyid=32bc1bee-a3f9-4c13-9c99-220b62a191ee&displaylang=en

    (it also seems that stuff developed "post VS2005" SP1, needs a newer runtime, than stuff developed "pre VS2005 SP1"

    @Rick: is this something required, and if so, the setup shim should probably take care of it if it doesn't already? (and if it does, then this whole post can be disregarded)

    (x64: http://www.microsoft.com/downloads/info.aspx?na=45&p=2&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=32bc1bee-a3f9-4c13-9c99-220b62a191ee&u=details.aspx%3ffamilyid%3d90548130-4468-4BBC-9673-D6ACABD5D13B%26displaylang%3den)

  3. Now, whenever paint.net crashes you get a pdncrash.log on the desktop, great!

    However, if a plugin crashes, there's no indication of what plugin/version that crashed, although the plugin can probably be extrapolated from the stacktrace. This info would probably be useful for plugin author. (To rule out the possibility that someone is using an old, buggy version)

    Or you might as well dump all AssemblyVersion, AssemblyFileVersion, AssemblyInformationalVersion attributes of all loaded assemblies if you want to go overboard :)

  4. BTW, one improvement could be a check box to choose if we want to start the interlace by 'black' or by 'picture' (with the checker it's based on the row I've selected)...

    Heh, I figured that such an option might be needed, but then somehow forgot about it.. I'll try to remember to fix that..

    And, it's the first plugin I see with multi language. I would appreciate to learn how to do that for my own plugins (source?).

    I'll post the source after I've done some cleanup.

    Meanwhile as a pointer, I just did it the standard .NET way, meaning you flip the Localizable property on the configuration dialog, and then switch languages and translate as necessary. Constant strings in the source goes into Project properties -> Resources.

    Not sure if this is how it should be done in Pdn though...

    Thanks.

    You're welcome!

  5. (For me, it was easier to modify my own code than to try and find the bug in yours. I was hoping you would be able to compare my code to your own in order to find your issue.)

    That said, I did manage to fix the preview issue with a little Reflector help..

    (How was I to know that I needed to call FinishTokenUpdate on every value change?)

    That is explained here: http://paintdotnet.12.forumer.com/viewt ... 4136#24136

    Oh, now I see it when I know that it's there (and now that it's not 1am)...

    8. Double-click on a new control and add "FinishtokenUpdate();" to the function. Repeat this for all new controls.

    That's how you do it "with hand holding", but from that you need to extrapolate that the double clicking a control will create a default event handler, that usually is some kind of value changed, and that calling FinishTokenUpdate is what tells the pdn that something has changed. I'd probably say something along the lines of "you need to call FinishTokenUpdate whenever a configuration option changes in order for preview to work properly".

    The "problem" with you posting CodeLab code was that it was not the effect code that was buggy, it was the UI "integration" with the effect code, and CodeLab code doesn't have that part... But anyway it works now.

    Another gotcha that I hit, that might be good to spell out in the plugin tutorial was the fact that you need to do

    dstArgs.Surface[x, y] = srcArgs.Surface[x, y];

    if you aren't modifying a particular pixel.

    I recommend you go back and update your first post to let people know that it no longer has an issue with the preview mode.

    Done

    Again, let me say "Good Job!" I'm sorry that I didn't help you.

    thanks, no problem!

  6. I mean when I click vertical on your effect, it does horizontal lines instead of vertical. Not which is the default it is doing.

    yes, I know, and I *think* that way (the original way that is) is correct 'terminologically speaking'. However, I see that the way you say is probably more intuitive for Joe User, so I uploaded a version where the Vertical produces vertical stripes.

  7. Thanks, this is cool, someone help him fix the preview.

    I already did.

    No you didn't, you rolled your own.

    Your attitude isn't helping anyone (especially considering this is my first publicly released plugin), and isn't exactly increasing my eagerness to make any new plugins.

    That said, I did manage to fix the preview issue with a little Reflector help..

    (How was I to know that I needed to call FinishTokenUpdate on every value change?)

    A new version is online, also with horizontal option

  8. I just created a interlace plugin, that adds horizontal/vertical stripes of configurable width and "color" (primary/secondary/transparent) to the image.

     

    Plugin:

      Download

     

    Sources:

    http://koti.mbnet.fi/tunedude/pdn/InterlaceSources.zip

     

    English, with Swedish and Finnish localization available.

     

    Version history:

    1.0.0.5:

    - reordered OK/cancel buttons to be in line with the rest of the software

     

×
×
  • Create New...