Jump to content

oblivioncth

Newbies
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

0

Recent Profile Visitors

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

  1. Ah my mistake. I was under the impression that C# primarily used an interpreter like Java (though that can be implemented as a JIT too) after being compiled to its intermediary, but it seems that C# is always compiled down to native byte-code on the target machine.
  2. Thanks for elaborating. I'd assume the tolerance percentage corresponds to this as some simple form of percent difference, but with 0 and 100% as exceptions to match only the exact color and match all colors respectively? Or is it as simple as 0% -> 0 and 100% -> 255? EDIT: Seems to be a simple scaling of x/100 = y/255 according to the magic wand source (with some additional quadratic shaping from "FastScale()" in its case). Man I wish C++ bytecode could be disassembled with this much detail in-tact . Obviously impossible since C# is i
  3. It probably is just so it's simpler, which would explain some of the oddities with it. That tool looks incredibly useful, is it this you were referring to? https://github.com/icsharpcode/ILSpy I'd be interested in using it to see more, particularly what distances are considered included for what percentages.
  4. I've begun studying it by seeing how many up-ticks of tolerance it takes for the next pixel to be affected in a gradient (of hue, sat, light, or combinations of them) where each pixel is only 1 higher/lower than the previous, but at the point I've gotten to it seems that the transform for whether a pixel is included or not is not linear (though this in part is most likely due to the rounding that occurs when ticking H/S/L up and down, perhaps I should start with just RGB. And additionally there will be some relative scaling due to the tolerance slider being percentage based) So, gi
  5. Imo this wouldn't make it anymore complicated for a plugin developer, though I can understand it does make the code a little more complicated. Perhaps my situation is just a bit specific and what I want wouldn't be helpful that often but: BoltBaits suggestion is what I do in my plugin now to get around this; however, my plugin largely has to do with doing HSL adjustments to match colors with its primary usage being to select the color you want to change as the primary color and the color you want to change to as the secondary color. Because of this I feel like it makes much more sense to simpl
  6. Ah nice! Thanks a bunch EER. This current plugin is pretty simple and while its effective it was also kind of an experiment for me in getting started on these plugins in case I want to make more. So for this one I'll just wait on Paint.NET to eventually update if they do end up putting this feature in; however, I can easily see myself wanting to do a more complicated plugin at some point that will need to make use of these.
  7. While working on a plug-in I realized that I have the same problem that ReMake talks about in that I'd prefer the Color wheel get reinitialized with the current Primary color each time the effect windows is brought up. I am able to use the strategy BoltBait mentions in that thread to get around its current behavior and always grab the primary color, or offer the user the option to use the primary color or the color in the wheel through a radio button group, but it just isn't as clean, especially since the color in the color picker won't get updated even if the user selects the primary color op
  8. Thanks for all of this clarification, its starting to give a me a good sense of things. I wasn't aware exactly what IndirectUI was until now but that makes total sense, its just the framework that exposes some pre-made UI options to plug-in creators, which also basically wraps up why CodeLab is setup the way it is. This also confirms my suspicions that more back-end work with the .NET WinForm controls would need to be used to acheive this. I can start looking into that as well as the library you linked. Great tip for leaving the description blank as that allows for a so
  9. Hi guys, I'm not new to C, but I'm completely green when it comes to Paint.NET plug-ins and the .NET framework. I was hoping that someone could give me guidance in achieving a color picker that also features an alpha selector for the simple plug-in I've been working on. The plugin is practically finished, and is entirely rigged up to work to spec on the back-end, but the small amount of alpha value manipulation I perform is currently nixed because of the way the default color wheel/picker for plugins functions. I've been following the development guidelines on the forum
×
×
  • Create New...