Ok, so this is also implemented.

Basically you call

include("test.js");

And it loads and executes the file "test.js" from the "Scripts" subfolder of the SynthPresets folder.

Nested including is supported and I wrote a simple protection system to prevent recursive includes (if you include two files in each other).

The code in the external file gets treated the same way as the code in the editor (live variable watch, autocomplete).

If there is an error in the external file it will get printed in the console (but the rest will compile fine). But actually you can expect that a external script file is tested and compiles correctly…

Ah yeah, that's a good approach.

:o :D

@3a2r9y2p:

ctrl + a to select all zones

Done

@3a2r9y2p:

mouse modifier to move zone up and down only (currently alt+drag is left/right only)
mouse modifier to move zone up/down/left/right all at once?

Done. This is a bit tricky because I am running out of modifier combinations (Ctrl+Drag is reserved for copying the samples).

@3a2r9y2p:

vertical zoom (so we can see individual velocities better)

Done. There is a mushroom button (inspired by Super Mario :)) that doubles the vertical size. If you want even more size, you could use:

@3a2r9y2p:

pop out map editor window so we can get a large viewing area / dedicated window, this is good for solving small mapping problems (mapping debugging)

Done. It is handled as internal popup (a overlay within the interface) - plugin host behave very funky when it comes to additional windows, so this is a pretty stable way to do it.
This feature is still a little bit buggy (there are many edge cases) - so let me know if you catch a bug with this one.

The current version is uploaded and can be found here:

viewtopic.php?f=3&t=6

I will check out the other requests now...

I think we should look at use case scenarios to figure out if there's actually a better way to approach the concept of having libraries with addons, all possible from a single master patch that senses which samples are present. For example, imagine creating a drum library that could be expanded with additional addon packs without needing to download a patch that addresses very specific ownership conditions (e.g. you own these two addons, but not this one…)

Having a missing samples indication is very important, though. If there are samples that are corrupt or in the wrong location, it's important for the user to know upon loading the library. That way they don't start playing and wonder why certain notes aren't playing.

Speaking of which, here's a semi-related request: the ability to purge single samples. Kontakt can only purge samples on an entire group basis. Maybe it isn't necessary with the whole containers thing, but just having more control over things like that would be a big improvement. It wasn't until Kontakt 5 until we could check the purge state of groups, even though you could purge groups via scripting back in Kontakt 4. So the lack of complete "getters" and "setters" for everything is one of those nuisances in Kontakt.