Jump to content

DataDink

Members
  • Posts

    23
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by DataDink

  1. What I meant by that was if you have a circle area selected you will end up with a square area that gets rendered. It wasn't until right as I was posting this that I thought about it but it shouldn't be a difficult fix.

     

    What you're suggesting is different though. This would require some kind of configuration to stagger the "row" or "column". So I'm thinking about what that would translate to configuration-wise.

    Maybe just be a checkbox to make a 50% alternating offset ? Can you think of a use-case where someone would want quarter/variable offsets (0%, 25%, 50%, 75%, etc)?

     

    The only concern I ever have is over-complicating the primary use-case of the plugin to accommodate edge-cases. It can lead to a frustrating experience 99% of the time to solve issues that only show up 1% of the time. Not that an extra checkbox would cause this to happen, you just have to stay vigilant because each little thing can add up quickly.

     

     

    Edit: Actually no, that wouldn't work - you would also have to adjust the row or column size to fit those pieces together. Another way to tackle that problem would be maybe a "radial tile" plugin that would let you configure iterations "around" rather than side-by-side. That might be a better solution maybe? What think you?

  2. Tile

     

    Source: https://github.com/DataDink/DinkPDN#tile

    Download: Removed for now -- see below, -Rick

    Developed on: PDN 4.0.6, NET 4.5.2, WIN 10

     

    TLDR: This takes the current image, selection, clipboard image, or externally loaded image and tiles it.

     

    Usage:

    • Select the area you want to tile across (or don't)
    • Effects -> Fill -> Tile
    • Adjust stuff

     

    004.jpg

     

    Options:

    • Horizontal Scale: This will adjust the width of the tile. Set this to 0 to keep it proportionately scaled with the Vertical Scale.
    • Vertical Scale: This will adjust the height of the tile. Set this to 0 to keep it proportionately scaled with the Horizontal Scale.
    • Horizontal Offset: This will cause the horizontal starting point of the tile to be offset from the left edge of the region.
    • Vertical Offset: This will cause the vertical starting point of the tile to be offset from the top edge of the region.
    • From Clipboard: This will create tiles using the image in the clipboard if any.
    • From File: This will allow you to load an externally saved image to tile.

     

    Known Issues:

    • This currently only works with rectangular selections/regions (Fixed)
    • Very small and unlikely memory leak identified.

    Notes:

    This has similar functionality to existing plugins. 

    Please feel free to contribute, fix, or fork this project here: https://github.com/DataDink/DinkPDN

    post-145003-0-23935300-1453528841_thumb.

    • Upvote 2
  3. No sorry on your part needed at all - you enlightened me to an issue I had never even heard of before. My intention is to promote easy community contribution to my project thereby relieving myself of responsibility that would ultimately lead to abandonware and reduce the value of my own contribution. What I now know is the label I have been using is better replaced with a "please feel free to contribute or fork this project here" link and let people call it whatever they want. So thank you for the enlightenment!

  4. It certainly is not my intention to offend and this is clearly a debate I don't want to be a part of so please feel free to apply whatever labels you feel are appropriate.

     

    Just want to include some "git" terms you will find where I have the source uploaded and the possible "freedom software" translations. Some of this will just be "source-control" basics if you are already familiar with the term.

    • Repository - This is a publicly visible location where anyone can access, study, and download the source code actually used to build the final product. You also have the right to do so. You can also feel free to use any of my stuff however you see fit as long as you don't try to hold me responsible for damages, or anything else, ever. Note: GitHub also offers private repositories allowing you to use GitHub services for your personal stuff that you don't want the world to see)
    • Pull Request - This is an actual code change you have made and can send to the project moderator who can choose to accept or deny this change to the primary / original project. This is usually accepted or declined based on if it is deemed something that the whole community is likely to agree is a benefit to the project they already know and love (maybe love).
    • Fork - You can start your own version of any project and base it on the original source allowing you to take it a different direction with no restrictions. You become the moderator of the forked project which can now be changed and redistributed as you see fit. The bonus of this is that you maintain a connection or lineage with the original project(s) and can then easily accept or deny changes from the original source as you see fit for your fork/version. With your forked project you will also build a forked community that sees things more your way.
    • Branch - This is like a fork but the intention is that it will be eventually merged back into the original project so going a completely different direction here is much less likely.
    • History - a memory of changes is maintained for every project, branch, fork, etc. Forks and branches can be made off of any of these points in history. Forks can also fork off of forks and still maintain the benefits of lineage without suppressing your rights as a free developer.
    • Contributor - This is someone who takes at least partial credit for the current state of the source code as it currently stands.
    • Moderator - This is someone authorized to accept or reject changes to a project (and so also become a contributor to the project)
  5. Nope, just using the base PDN libraries. The plugins I'm making right now are simple automations of what I have been doing manually for years. I am only now just starting to explore building a library for myself to start streamlining some of my existing PDN workflows. With that said I am simply wanting to share what I make with the community in case someone else can benefit from it. So I don't mean to sound inconsiderate when I say I will probably not invest time in compat for an audience that will soon dwindle away due to natural technological progression.

     

    I am, however, making every effort to ensure that these plugins are truly "open source" allowing anyone to make such contributions via well-established technologies such as those provided by the open-source community at github.com.

     

    P,S, I do wish there was better "official" documentation on the PDN libraries. I'm currently reflecting into PDN libraries and tracing code paths with a fair amount of sadness.

     

    (and I really do VERY much appreciate the community you guys have built around PDN. Bravo!)

  6. You're a really good moderator. Thanks for being so informative. I don't have compat info, but I did add the environment developed on for reference.

     

    Question: What makes compat with old versions relevant? Is there something keeping a portion of the community from upgrading to latest versions?

  7. Your screenshot shows this as an Adjustment. I (eventually) found it under Effects > Color. I trusted you - and now the Plugin Index is wrong!!  :lol:

     

    Would you be so kind as to *clearly state* where the plugin can be found (in the first post) and update the screenshot?  Thank you!

     

    Aaah! I have abused your trust!

     

    Yes, it was originally under adjustments until I was informed of the "Color" submenu, standardized by the community. (The community around PDN is FANTASTIC btw). I have fixed the post with the offending lies and redirected it towards truth and light!

    • Upvote 2
  8. Blend Seams

     

    Moderator Note: Here's a compatible release for the latest versions of paint.net (beyond 4.0.10).

    Download

     

     

    Source: https://github.com/DataDink/DinkPDN/blob/master/README.md#blend-seams

    Download: https://github.com/DataDink/DinkPDN/raw/master/Binaries/BlendSeams/Latest/BlendSeams.dll

    Developed on: PDN 4.0.6, NET 4.5.2, WIN 10

     

    TLDR: This will attempt to smooth out the edges of a texture that isn't already seamless in hopes to hide the seam

     

    Usage:

    • Select a single iteration / tile of the texture
    • Effects -> Render -> Blend Seams
    • Adjust stuff
    • Tile the result side by side to see the results

    Demo1.jpg

     

    What it does:

    This plugin uses the center of the tile to smooth out the edges of the tile. The assumption is that the center of the tile has no seams and can be used to create blend points on the sides of the tile. 

     

    Notes:

    This plugin is open source. If you want to fix something or improve this plugin please feel free to send me a pull request at https://github.com/DataDink/DinkPDN. I will accept anything that isn't too far off from the original "intent" of the project.

    post-145003-0-85158600-1451612940_thumb.

     

    • Upvote 9
  9. Sure, that's fine. I'm just trying to get in tune with the community here. We'll keep it going then :)

     

    Also please note that this plugin is open sourced. What this means is if you've identified a fix or would like to add to the project you can do so yourself at https://github.com/DataDink/DinkPDN/tree/master#color-cut

    I will accept any pull request that isn't too far off of the "intent" of the project.

  10.  

    Just add a line

    control.SetPropertyControlValue(PropertyNames.AlphaFalloff, ControlInfoPropertyNames.DecimalPlaces, 3);

    before the line

    return configUI; 

     

    Hi Remake,

     

    This has already been taken care of and is ready for (re) download.

  11.  

    Hello DataDink, and welcome to the Forums!

     

    The increment of Alpha Falloff control doesn't work correctly for me.

    I think the error is in this line:

    control.SetPropertyControlValue(PropertyNames.AlphaFalloff, ControlInfoPropertyNames.UpDownIncrement, .001d);

     

    Hi Remake,

     

    I would be interested in seeing a full stack trace of the exception if you have one available. This would give me better context as to why this is failing for you and not for me.

     

    EDIT:

     

    Nvm - I understand what you are asking now. It appears the displayed precision is limited to displaying only 2 decimal places. This results in a higher precision being available with the up/down buttons, but you can't actually see the 3rd number after the decimal. I'll see if there is a way to display a higher precision. I really do think, however, anything this plugin has to offer could be accomplished with the "Color Replacer" mentioned earlier in this thread.

     

    EDIT:

     

    Updated.

  12. Another plugin to remove and/or replace colour and/or background. Thank you very much DataDink and welcome to the forum.

     

    Regarding the placing of your plugin in the Adjustments menu, please read below my reply to another colour plugin, Color Replacer, published recently:

     

    The "Color" sub-menu isn't among the defaults listed by the "PaintDotNet.Effects.SubmenuNames" and I'm guessing is a fabricated sub-menu by the community. Knowing that this is an agreed upon / standardized name I agree that it would be better there and wonder if the Colors name should be added to the defaults in a future update/patch of PDN.

     

    I would actually just rather get input on the proper way to depreciate this plugin all together. Is deleting the entire thread acceptable to the community?

     

    The only reason why I made ColorCut is because (probably due to my inferior searching skills) I didn't find a plugin like "Color Replacer" to solve my problem. It would be better, in my opinion, to focus feature requests towards "Color Replacer".

     

    Sorry for being so new to your community and thanks for the feedback! Knowing how active you guys are I'll be sure to just ask a question next time.

     

    EDIT:

     

    Updated.

  13. Hi

     

    To be honest, with how the internet is today, I half expected nothing but flaming, trolling, raging, and hatred - so thanks for the warm welcome!

     

    The TLDR is: This is another green-screen plugin.

     

    Here's the long version:

     

    First you'll want to set the secondary color to what you want removed. This can be done by right-clicking with the Color Picker tool:

    Untitled.jpg

     

    Next you can adjust the color and shade sensitivities to grab the range of colors around your selected colors you wish to remove.

     

    002.png

     

    The Color Threshold will set the variance in color that will be removed

    The Shade Threshold will set the variance in shade that will be removed

    And (the reason I made this plugin) the Alpha Falloff will control the "hardness" of the effect.

     

    So hopefully when you are done you have a nice cut-out with blending, non-jagged edges:

     

    003.png

     

    Green-screen is the simplest usage of this plugin. I created this to to cut objects out of detailed backgrounds that were not intended for cut-out. 

    post-145003-0-55077700-1451367344_thumb.

    post-145003-0-54756700-1451367351_thumb.

    post-145003-0-26941800-1451624031_thumb.

    • Upvote 4
  14. Moderator Note: This plugin is incompatible with the latest versions of paint.net (beyond 4.0.10).

     

    Please see a newer version 5/1/22 here: 

     

    Hey guys!

     

    Decided to try my hand at one of these here plugins. Sorry if I'm newbing it all up. 

    This is similar to other "green screen" plugins, but it uses the secondary color and allows you to configure tolerances. Mainly what I was after in this plugin was the ability to control the "softness" of the effect which you can configure using the "Alpha Falloff" setting.

     

    Source: https://github.com/DataDink/DinkPDN

    Download: https://raw.githubusercontent.com/DataDink/DinkPDN/master/Binaries/ColorCut/Latest/ColorCut.dll

    Developed on: PDN 4.0.6, NET 4.5.2, WIN 10

     

    Version 1.0.3

    • BugFix: Shade threshold is now based off of "Brightness" (setting is now more meaningful)
    • Moved to new DinkPDN codebase (preparing to make moar stuff)

     

    • Upvote 4
×
×
  • Create New...