I realise I'm not the one writing the software (although I am a software writer and I am extremely impressed by MuseScore - thank you) and I don't know how much of a problem it is to implement. Probably when a play related command is issued by the user. The view to change to include the note that is about to play, rather than the one that is currently playing (might have the same effect). Possible other ways of potentially achieving what I would prefer: As a software user, I don't like clicking on things and having no confirmation that anything changed. Personally, I want to see what is going to be played next, as I can when MuseScore is playing. I also always have an 'arrrrgh' moment when I click rewind and nothing appears to happen. Especially, as previously noted, playback moves it. It may not be the software author's original intention that the rewind button should also move the score but it seems intuitive to me that it would do that. I know this thread is about 3 1/2 years old but i have to say that I agree with BSG and shoogle. If we tweak Rewind, fine, whatever, but it doesn't address the actual problem with the discoverability of navigation functions, especially for users with no Home and End keys. To me, those are the real problems that need solving. Even if we tweaked the behavior of Rewind, it doesn't solve their general navigation problems. The *real* problem is the second case - the person hitting Rewind because it's the only way they can figure out how to get back to the beginning of the score. Again, I have nothing against changing this, but it seems inconsequential to me, and misses the *real* problem. Personally, I don't mind the extra "think" time still looking at where I am. So it's at best a very minor nuisance that it doesn't do it until a second or two *after* you hit Rewind (or however long it takes you to get around to pressing Play). And you said yourself, that's the next thing you were going to do anyhow. You don't have to hit Home - it already homes itself when playback begins. I, on the other hand, am talking about someone who may have no interest in playback whatsoever, but is hitting Rewind because they don't know how else to position the score at the beginning.įor your case, there really is no problem. For that person, yes, they are likely to hit Play after Rewind - because that was their *reason* for pressing Rewind in the first place. You are talking about someone who actually is interested in playback. We are talking about two different problems. But I don't really any obvious reason why "rewind" should automatically also do a "home" any more than the reverse. A separate toolbar with Home, End, Page Up, and Page Down commands might be a useful thing - especially for people on Macs or Chromebooks or other keyboards that lack those keys. It provides commands relevant for playback, not for score view positioning. The playback toolbar doens't provide a full set of score view positioning commands because it isn't meant to be used for that purpose. The point, though, is that "Rewind" is a plyabck command. I personally never saw rewind reset the score view, but then, I rarely use that button - I use Home to reposition the score. To me, that is a bug, although a minor one. But in 1.3, this would "sometimes" cause the score view to follow even though you are not in playback mode, and sometimes not. In both 1.3 and in 2.0, the button always achieves its primary purpose - resetting the *playback* cursor. It's probably more appropriate to say, it something bug if it behaves in unpredictable ways. That is using UIApplication's beginReceivingRemoteControlEvents.I was being somewhat facetious in calling it a bug.
0 Comments
Leave a Reply. |