Peter L Jones

What do you mean? Currently the build on main runs. Without the workaround, it didn't run. So the workaround on main is still there. The issue is that it's a...

Um, interesting... I wonder what changed.

https://github.com/jamulussoftware/jamulus/actions/runs/11367998339/job/31622018160#step:3:2 ran okay... https://github.com/jamulussoftware/jamulus/actions/workflows/coding-style-check.yml In fact, up until your last couple of builds, it looks to have been okay. I can only guess the action is using something that's not...

I don't like it being unstable... I thought we generally pinned versions of the actions to avoid things like this? Or is it not the action itself?

#3415 raised to try the revert. https://github.com/jamulussoftware/jamulus/actions/runs/11521963146 manually run for revert.

Had a go: https://github.com/jamulussoftware/jamulus/pull/3378 ``` man linux/Jamulus.1 ``` to proof read it. On your handy Linux partition.

Not that it's much benefit in the long run. I had, as part of my rewrite of parsing the command line options, added a feature that supported documenting each option...

The main issue is the move to Qt6. I think that should be addressed separately. If this change _requires_ Qt6, then it gets blocked until we've made the decision to...

There may currently be a problem with `CSoundBase::ParseCommandLineArgument` in that it doesn't necessarily set every element of `aMidiCtls` for each `sMidiCtlChar` but it doesn't check in `CSoundBase::ParseMIDIMessage` that the element...

OK, so I decided to make the change I suggested. Once the build is complete for Windows, I'll give it a try here. ---- The legacy definition has just one...