MS 3.1 -- What happened to "Midi Input: none" !?

• May 28, 2019 - 23:59

OS: macOS Mojave (10.14), Arch.: x86_64, MuseScore version (64-bit):, revision: e26f7c4

The long-hoped-for change didn't see to make it in .... sigh.


In reply to by BSG

The schedule that Anatoly said was planned was about a 3 week update cycle for minor releases and major releases as necessary. There must be issue with it or I think ABL would have pushed to have it merged for 3.1. I can only speculate that this has not been forgotten since there is recent activity on GIT for the issue. Perhaps it can be finished for 3.1.1 when it gets released in a few weeks. You would need to get ABL's attention for a better update.

In reply to by mike320

(Older) relevant comments from pull request's author at the pull request page:
- "I think this PR has to be thoroughly tested" Which is why suggested BSG contract the author for a test build.
- "From the tests (see the related issue), the "none" preference does not survive at the third launch of the application. I will further work on this.
So this is at the moment still a work in progress, please do not merge yet." Which is why the pull request is marked "work in progress".

@BSG, you could comment on the pull request itself.

In reply to by RobFog

As a career programmer, I know the inadvisability of commenting on the code unless I both (a) test it myself and (b) understand the context of the code sufficiently to find problems. I'm not (yet) willing to get into either the github or build-it-myself business, but either or both of those times may come. Both Ziya and I are competent to test it (we both "need" it), and have tested it. The text you quote correctly notes the last problem that was found (by both of us), and there has been no available build to test since. Ready, willing, and able to test one as soon as @ABL is RDY and WLG, too...

In reply to by BSG

I had posted a build in which I think the resetting was solved, did you manage to test it?
Ziya replied that he could not download for a gmail problem: is it so? Should I re-upload those builds?

As I try to describe in I think this new build should solve the problem, but there is still a situation I don't know what is the expected behavior from a user's point of view.

Do you still have an unanswered question? Please log in first to post your question.