Brett
Anderton
You may be right, but I don't recall seeing anyone say that. I have, however, seen some staff view proponents theorize that people who aren't interested in staff view feel that way, which I think applies at most to a small minority, if at all. Also speaking of small minorities, some staff view proponents come off as thinking they're more sophisticated for using it and feel those who don't aren't "real musicians."
Of all the feature requests and bug reports made, staff notation is the only one that is actively opposed by anyone.
You did not include what I was responding to, so you are not addressing my point. I was responding to this, which I quoted in my post:
Anderton
Kev999
I get the impression that some users are taking a stance against Staff View because they apparently think it belongs to some elite set that they don't want to be associated with. Maybe it's not rock-n-roll enough.
You may be right, but I don't recall seeing anyone say that.
So are you saying people were indeed objecting to staff view because they "think it belongs to some elite set that they don't want to be associated with. Maybe it's not rock-n-roll enough"?
I tend to think it has more to do with people who don't consider it important in their own workflow, realize it would take resources, and would rather see those resources committed to features that matter to
them. Is that assessment wrong? Can you point to any posts from people who object because they think "it belongs to some elite set that they don't want to be associated with?" I just don't associate that kind of mentality with this community, by and large.