DataDink

The rendering issue has been fixed. Plz 2 redownload

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?

I'm confused. Is there an objection to a consistent user experience?

Jeeze

There's a virus site?

<snip> And: http://forums.getpaint.net/index.php?/topic/12831-tile-fill-addin/

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 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

That's cool! Thanks for sharing that!

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!

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)

That's a new one - can you elaborate?

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!)

ic, thx for the info.

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?

Tried this out on a bunch of misc images from the internet. Some of them turned out ok, some of them meh. I was overall happy with it so I thought I would share...