From: D. M. M. <mic...@ro...> - 2010-01-15 07:17:36
|
On Friday 15 January 2010, Jim Cochrane wrote: > Open a non-empty track in the notation editor. Non-empty segment from just one track. (Just one staff.) Check. > (I suspect the behavior will be the same with > 1 track.) At > 1 track/staff the view should open initially in a smaller font by default, so I would not expect the behavior you described in that case. > Click on Segment -> Add Layer. Check. > (BTW, I'm not sure exactly what this is for, though it looks like it may > be a tool to help with working with multiple parts on the same staff.) Right. If you find you're encountering a situation that has to be drawn using multiple separate segments (eg. a guitar part where the bass notes ring out as half notes mixed with 8th note arpeggiated chords) you can use this gadget to create a new segment right where you're sitting, bring it into the current notation view, and activate it for editing in one step. This is a huge improvement over how this used to have to be accomplished, which muchly suckethed royally. > When it finished processing, the font was larger. (I think it was the > default size - 8?) But the reported size was 6. I changed it to 4, > which worked, and then back to 6, which also worked. (I.e., it was > really 6 at this point.) With defaults in place, the view should have opened at size 8. The multi- staff font size is 6. It sounds like what you saw was that adding a layer convinced the notation view that there was more than one track, and it switched font sizes on the fly. I wouldn't actually expect that to happen without closing and re-opening the view. Also, I'm supposed to have fixed this, so if there is only one staff, even if it has 40 segments on it, the single-staff font size will be used. In practice, I tried to repeat this several different ways, and was never able to do so. It always opened at size 8 and remained at size 8. If this bug exists, there's something more to repeating it than meets the eye, because all the code appears to be working as intended in 11642. I imagine if it is possible to repeat this though, it somehow involves Rosegarden thinking the new segment is on a different track, and/or there's some track-related bug at play here. I can't get anywhere trying to reproduce it again with ideas like that in mind though. Hrm. -- D. Michael McIntyre |