100 is not a user value... You got lucky so its currently not used...
function AllocatePluginKeyRange(1, False) returns unique free values.
Or start from ecUserFirst upwards.
Are you saying there could be a short-cut collision between the default Synedit short-cuts
Yes and no, more no...
There is a difference between the shortcut and the command.
E.g. if you use syncro edit, then the same shortcuts are changed to become other commands while syncro is active....
-------------
So what happens:
Stage 1: Translate shortcode (the keys from keyboard) into a command.
Stage 2: Execute the command.
If you have 2 completion dropdowns, and they both translate their keys to the same command, then it is no longer known what keycode was used, or which plugin did return the code.
That happens even if you use keys, that aren't used by SynEdit at all. The problem is the overlap in the command that is found.
The reason is that commands can also be injected by user code. You could have code that injects the command to start completion, based on stuff going on outside of synedit....
Or you can set up mouse clicks, that will execute commands. ...
And, if you use multi caret, then some commands are intercepted, because they wouldn't work. So the 2 phase about have to be done completely independent of each other.