> Originally I called it "Select beats", but then I realized that that was > misleading since they're not actually beats yet.
"Guess beats" maybe? > I agree that "unadopt" is not so obvious. My head was still in the code > when I wrote that string. Plus it's not a word in English and sure isn't easy to translate. It's just some internal tech speak gibberish. > 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? I kind of like leaving it tech speak gibberish in a way. On some level, it strikes me as more honest since this is an extremely obscure, highly advanced feature. > 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. Why do you want a variant of NotationSelector that doesn't follow ties? I made the thing follow ties because breaking ties leads to broken things and headaches and general vileness. Treating tied notes like single units was a big improvement, because they ARE effectively single units. I just hope whatever context in which you feel you need this is smart enough to remove all the mismatched tied_forward/backward properties from severed things that are no longer connected. The inappropriate properties are what screw things up. -- D. Michael McIntyre ------------------------------------------------------------------------------ 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
