Hey there! Thanks a lot for the suggestions and the bug report.
I could have sworn, I had the whole outAIne thing patched out before it saw the light of day, I even ran a replacement command over the entire thing.
I’ve also just changed the cancel button logic. Completely went past my radar, for some reason, I was using the cancel button to reload things for a long time. That’s embarrassing. 
Now to address your recommended visual changes.
My biggest driving factor in the visual design of this extension was to give instant visual feedback to any and all changes made. So if you change any of the strength sliders, change a value somewhere, you’d see what exactly your change does. I do see a point in hiding a lot of the buttons and shades, if the user knows what they are doing.
For that reason alone did I include this many presets, so the interpolation drop down menus wouldn’t overlap with any of the shades. (If you can’t see the change, it’s hard to make adjustments)
That being said, I have an idea to replace the interpolation functions with bezier curves and replacing the drop down menus completely with sliders.
That being said, I’ve only included drop down menus, because I haven’t come up with a better way to change the interpolation method at the time.
The reset buttons function is a bit of a failsave. If something happens to be messed up, you can go back to how the tool looks on startup without opening it again. It also wipes the clipboard.
For that matter, you could say the reload button is also a failsave, in case something got updated that I haven’t accounted for. I’ve had glitches that required both of these in the past. That being said, maybe they aren’t necessary now as they used to be, but I prefer to keep them.
Even if I add a combobox to control which shades to show and which not to, given my visual design philosophy, at worst, it makes the maximum height of the window even taller. I do agree with the notion to reduce the height, but at this moment, I’d be more likely to remove either the values or the lightness shade lines to achieve this.
When I get the time to do a bigger rewrite, I’ll remove at least one line of presets, if it’s not possible to save them as .json files somehow.
That being said, I’m slightly confused about the presets section in your mock up and how that’d work. Since every preset besides the custom ones have values assigned. Would you put two thirds of them in the combobox, while leaving the rest out?
Maybe I’ll create a second window to put the presets in. I don’t know yet. I’ll have to give this more thought. Ideally, everything would be in one(ish) place.
I see why you’d want to have an input box for the strength, but this again goes against my design philisophy. If you’re working with your tablet, it’s easier. Yes, I can save half the space, but it’s going to be hard(er) to control with touch and tablet. For that matter, I also wouldn’t really be able to put them all on the same line, because it would be harder to set to a specific number.
I know my response probably looks like a lot of different flavors of “no”, but I’m taking your suggestions to heart. Originally, the tool was supposed to be much smaller/straightforward, but I kept on adding ways to give the user more control, and this list will probably not shrink. Maybe if I was able to put all the shades into their own window, that’d make things tidier. I’ll go over this problem hopefully soon.
Oh and also, how did you get the minimum window height of 984 pixels? At 100% aseprite scale, the window should only be 602 pixels high. That’s more than 50% taller than it’s supposed to be. Here’s the window in native resolution:
Even if you have only a 720p monitor, it should be able to show the entire widget.
Either way, I fixed the outSine bug and gave the Cancel button its intended purpose. I’ll have to do something for a friend and then I’ll get to adding the left and right base colors to the shades output. =)
I’m sorry the widget is such a mess. ^__^’
thx