> Lots more new work than I was expecting!
>
> Here are some strings that jumped out at me, because I have no idea what
> they do:
Writing clear text has never been my forte, so please feel entirely free
to suggest anything that makes more sense.
> Select evenly spaced notes (total mystery; evenly spaced how? selected
> how?)
Evenly spaced in time. The use case is that you use "Select Evenly spaced
notes" to capture notes that would make a good beat segment, and that
means evenly spaced notes in time (approximately).
"Select" is just normal select. After the command they are displayed
blue, NotationView's getSelection() is holding them, the usual.
I didn't mean to make it mysterious. I'm open to any suggestions for a
clearer string.
Originally I called it "Select beats", but then I realized that that was
misleading since they're not actually beats yet.
> Unadopt an adopted segment (adopting and unadopting segments? huh?)
Background: When I wrote that thing that lets you edit ornaments inline,
NotationView does it by adopting segments that really are copies or links
of ornaments. NotationView shows them, and you can even edit ornaments
that way.
I provided a command to hide them when the user doesn't want to see them
any more, which is "Unadopt an adopted segment".
I agree that "unadopt" is not so obvious. My head was still in the code
when I wrote that string.
That menu item is only available when the cursor is in an adopted segment,
so it could be just "Hide Segment". Would that make more sense?
> Select but don't follow ties (don't follow how? select how?)
That's the menu item of a variant NotationSelector that doesn't follow
ties. Ie, if you lasso a note N1 and it's tied to another note N2, only
N1 gets selected.
Do you find "Select but don't follow ties" clearer when it's presented in
the context of the "Select" tool? They live in the same menu. If it
makes your life any easier, I could write a translator note so the string
isn't sitting out there with no context.
> G (what's this G for?)
Oops! "tr" was a mistake which I will fix.
If you're curious, it was a holdover from when I used an actual text
string to indicate an autogenerated region (Made by
ExpandFigurationCommand). It got quite cluttered so I reduced it to a
single letter. I should use a proper symbol, but I forgot.
Thank you for pointing those out. Please tell me anything else that's
odd, because I don't mean to make my text mysterious.
Tom Breton (Tehom)
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
