I'll take the issue http://musescore.org/en/node/30941 as an example (but
other examples exist and more or less anybody met this anomaly once) and
specifically the sample score posted in the thread last comment (
http://musescore.org/en/node/30941#comment-129056 ):
I think (part of?) the problem r
Some update on the current status of the plugins:
WORKING (including those depending on open pull requests):
- Note Names (https://github.com/Jojo-Schmitz/notenames)
- Cue Notes (https://github.com/Jojo-Schmitz/Cue)
- Blacknotes (https://github.com/lasconic/blacknotes)
- Color Voices (http
I think "break every x measures" does work, it does for me? Ah, I see, just
the undo doesn't work.
Sorry about "Color Notes", I had added your grace notes fix but had
forgotten about that last measure thing... It does work though, even if
having that bug.
Add/Change in your list:
WORKING
- Note
I'm not sure what you mean (Jojo) by prototype. Repeat List is working fine on
my computer, but needs the PR #1271. This version has basic features (listing
all the measure in their playing order, associated time and utick) but still
lacks a few features to be more complete.
The PR #1271 does
I created pull request #1277 to fix the problems with "break every x measures".
--
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
___
Mscore-devel
Hi Stéphane
I wasnt sure, because I didnt test it. Now we know which category it falls
into ;-)
You can force Travis to retry, by git commit amend; (save the commit
message unchanged); git push force. Sometimes you may have to do that
several times
Bye, Jojo
-
Thanks for looking into this further!
> *Measure::minWidth1()* and *Measure::minWidth2()* do not take any cautionary
> / courtesy element at the end of the system into account to compute the
> measure width; nor should they, as these functions are agnostic about the
> context the measure is in.
A
Marc Sabatella wrote
> Thanks for looking into this further! [...]
>
>> I see two possible strategies:
>>
>> 1) *Score::layoutSystem()* checks for potential courtesy elements before
>> adding another measure to the system.
>>
>> 2) *Score::layoutSystemRow()* checks for available room before adding
> I created pull request #1277 to fix the problems with "break every x
> measures".
Unfortunately it seems to be not that simple. I was able to compile my branch
here, because I already had some header files generated from a previous
compilation. When compiling from scratch, it doesn't work.
