Matthijs Kooijman

I'm also working on making the documentation on plugin parameters in the manual complete, I'll add a commit (or maybe separate PR) to document this change as well when it...

I realized that there are actually two ways to identify a plugin: 1. The user-visible number, usually named "piid". This is a 1-based index into the list of visible, non-channelstrip...

One related improvement could be to also allow libraries to define such "menus" or "options", that can be configured by the user. This probably needs some other way to specify...

Also, often such "incompatible" libraries can still be made compatible by e.g. including an "ImprovedFoo.h" or "OriginalFoo.h" header file that is unique to the improved and/or original version, so a...

No longer allowing comma-separated values seems like a good solution here. There should usually not be any problem with just supplying the option multiple times, and using a comma to...

> everything seems to work unless some code uses ARDUINO_ARCH_{build.arch} pattern. Also, I think core references do not work (e.g. `someboard.build.core=arduino:arduino` or something like that in a derived core that...

This would indeed be useful to have, but probably requires some changes to the programmer/tool specifications. As for adding these as part of the `-P` programmer option, that does not...

> in avrdude you specify -PUSB for a device on a USB port and programmers.txt maps VID:PID to use I actually think the vid-pid to use is hardcoded inside avrdude,...

> As I pointed out above, if a device is configured as an HiD peripheral you won't have a U(S)ART available, and this wouldn't work Yeah, I meant that *if*...

I just upgraded to 0.83.0, which contains #8632, and it seems this bug is not entirely fixed. As suggested by the commit message, it now works for code blocks that...