@lasconic:
Is there a plan of the features planned to be included / developed for
MuseScore 2.1?
Another question: if we keep two branches next release and stable
release, which will be the target of the PR?
If we take the Qt model as an example: they have a tree of branches and
they suggest to
A plan for 2.1. Yes, sort of. More a plan for the next two or three major
releases. I still need to publish it on musescore.org. Also, the plan is to
adapt if someone is motivated enough to work on something that we didn't
think about.
I like to refer to the Qt project but I also understand we
First of all, I have no suggestions on the maintenance points.
About the main topic, FWIW I also believe that bug fixes are always welcome!
With a few notices:
1) Users do not always care (or even know) about product versions (many do
not even care about which OS they use...). I assume that
Hi Marc, yes you are right.
I'm in the very early stages of my development. But I believe the approach
i'm taking will lend itself very easily to chord realization as well. I'll
make a special point to talk to the student about this and coordinate
efforts.
--
View this message in
Jim Newton wrote
So I experimented with playback and it indeed sounds horrible.
What I want to do now, is something like the Explode command.
This I'll have musescore translate the encoded Figured Bass into notes on
a staff which the user can then manipulate manually.
Does not sound simple...
BTW does the Figured Bass notation in musescore support the tasto solo
keyword?
--
View this message in context:
http://dev-list.musescore.org/programmatic-access-of-figured-bass-tp7579343p7579381.html
Sent from the MuseScore Developer mailing list archive at Nabble.com.
@Jojo
1- Because branch are cheap and it feels right to have a branch per
release. It's the same model Qt has for example.
4- We could try to remove no-obsolete. However, MuseScore 2.0 and MuseScore
2.0.1 are currently downloading translation files from different
directories. My plan was to
lasconic wrote
1- I agree that too short delays have consequences. However MuseScore has
an update checker and it will nag users every week or so to upgrade to a
more recent version. Also, I prefer having more user support to do with a
simple answer (Please upgrade) than not having a good
Jim Newton wrote
BTW does the Figured Bass notation in musescore support the tasto solo
keyword?
In which sense? By definition tasto solo passages have no figures, so
there would be nothing to store the flag into.
--
View this message in context:
