JoergAtGithub

For the single controller use case I can imagine two solution: 1.) Multiple mappings share one XML-File but the different controller scripts remain unmodified. Than we could declare the shared...

I wonder if it wouldn't be better to decalare each shared variable instead of just the namespace. While more text to write, I think it would make it more clear...

> > Do we need backwards-compatibility aliases for controls that are not documented in the manual? > > IMO no, any included mappings should be fixed via search and replace,...

Please think about users without programming skills, which have downloaded, or will download mappings from our mappings forum. Now these mappings are useable - even if the mapping is unmaintained....

The documentation of the COs in the manual is incomplete, therefore it's not suitable as criteria. But there are also COs, which are not useful for mappings or skins, there...

> I added a column in the CO table above. Please have a look. If you think that any COs which are marked with ❌ should be aliased, let's add...

Two minor remarks regarding the floating widgets: - It's sometimes difficult to distinguish the colored widget from the waveform which has the same colors. A border in a different color...

I suggested to move the floating widgets in an own PR, to not block merging this PR and the PRs before. I'm not against these widgets, I just expect a...

> > fx standard disabled when a track is loaded > > I will look into this. There is already a setting for mute/volume, so it makes sense to extend...

> @JoergAtGithub How does the testing succeeds on your side? Since we don't officially ship QML anyway and my Qt is outdated it shall not block the merge. My last...