Upward cross staff beam displays incorrectly
First reported by TGV: http://musescore.org/en/node/1084#comment-5845
When I tried cross staff beaming, I found that going down went as expected, but going up gave the weirdest results. The change would not be visible at once, and after selecting another note, the affected note would appear on the wrong line. The following demonstrates it:
1. Open the document "Test.mscz
"
2. Click on the first G in the lower staff
3. Give the command for cross staff beaming (ctrl-shift-up, or cmd-shift-up in my case). Note that there is no visible change
4. Click elsewhere, or type the left-arrow: suddenly the note selected in step 2 will move to a higher E in the upper staff, while the stem stays in the lower staff. The note can no longer be selected by clicking.
5. Now select another note in the same beam and type 'x': suddenly everything is all right.
Test environment: MuseScore 0.9.5, MacOSX 10.5.8, iBook G4
Comments
this is fixed in rev. 2032
Automatically closed -- issue fixed for 2 weeks with no activity.
This may be petty but I would appreciate if the "closing of an issue - no report for 2 wks" was contained in the issue title so I wouldn't need to check everything to keep as up to date as possible.
Thanks, and best regards.
Don
Hi Don,
I'm afraid I don't understand what you exactly wish to obtain with seeing the status of the issue in the title.
The only thing I currently see for optimization is 'not' to send an email when an issue is being closed. Do you concur this might solve your problem?
Yes.
Many times I open a message only to find no new info. Not seeing those messageds would help.
Thanks.
Don
Simple answer for this one: someone spammed this message and enough people did the "mark as spam" (including me) that the users message was removed. If you see a topic, esp an old one, where there appears to be no new postings you can safely assume that someone spammed the group and his post was removed.
(Ugh! I hate it when I respond to something without closely checking the date of the last post first!!! I would have seen that Xavier's last post was 2009.)