Right! I didn't think of multi-track-changing
Wouldn't it be better that, on Notification, it can be retrieved somehow that more than 1 song "is about to be changed"?
boroda74, That would also make it work with your plugin, right? So, that there is only 1 notification at the end of all changes (or none)?
I am also thinking of Musicbee's own multi-changing possibilities (now and in the future). It gives the same problem already.
That's why I think the "multi"-approach is better then the manual/interactive/API differentiation, if I understood the latter right.
Though I figure that then plugins will have to tell Musicbee themselves that more tracks "are going to be changed".
Maybe an API multi-change function (via a collection, List, Dictionary or array with sourcefiles and desired changes) would cover that? (That can be handy anyway, right?) (Or similar, but via callback. Or even better multi-changing API support.)
Anyway, Steven? *shout*
P.S. Thanks, boroda74.