Regarding 1., what would be a justification for this rather arbitrary limitation? I think the most usual usage of the keyboard map is to "paint" whole regions of notes, f.e. to assign notes C-5 to C-6 to a given sample. Why should this assignment only apply to the white keys? Why should it need me to do two assignments (one for black and one for white) to accomplish this job? I honestly can't imagine of a situation where it would be an advantage to only paint over the black keys or only the white keys. Usually you wouldn't want to assign one sample to black keys and the other to white keys only.

The main problem lies when one wants to assign ALL keys in a range (including black keys) but the user has accidentally not slid over all the keys -- such as along the bottom half where he has selected only the white keys. If he then attempts to go back over and slide across the black keys so those are included, it will, because of the nature of the graphic input, also DEselect the white keys.

A Reset button would solve THIS more usual scenario (as long as previous assignments are not erased), but for those rare circumstances when you do want a sample to fill only the black keys in a range, dividing the keyboard input zones (or adjusting the keyboard "buttons") would allow for greater functionality.

However, i myself would just be happy with a Reset button that reverts the assignments to what they were before editing the sample map. Or even better an Undo series for the duration of the dialog display...

I don't think black vs white key separation is the solution to the problem. It would be more logical to make a mouse click not invert the current selection, but rather apply the same actions to all keys that are covered by the same mouse action. So if you click a key and assign a sample by clicking, dragging the mouse should assign the sample to all other hovered keys and not simply invert their state.

Sounds good for a future build. Thanks.

I have implemented the suggested behaviour from comment 0000244:0000720 now: http://sagagames.de/stuff/mptrack.exe

Doesn't quite work.

When clicking on an empty key, all keys you drag over will indeed turn them on, even if they're already on. When clicking on a key that's already set, the old behavior is called. Still half-broken.

It's not really the old behaviour, it's just a "smart" behaviour that I intended to implement - apparently it's not as "smart" as I wanted it to be, though. This will have to be revised.

Now everything should behave as intended.

yes, but see 0000342

I'll close this then.