4 ms·

> is it a "power-user" feature to want the buttons the opposite way around? That's supported. What isn't supported is mapping arbitrary buttons to arbitrary f

> is it a "power-user" feature to want the buttons the opposite way around? That's supported. What isn't supported is mapping arbitrary buttons to arbitrary functions because that's a hard problem to solve generically: see Evoluent having to ship their own customization software for Windows and Mac instead of just using OS configuration screens.

alias_neo 8y ago
My example isn't the greatest, I agree, because it is, generally supported everywhere. A more appropriate example might have been scroll-bars, very few devices support moving them to the left. particularly when it's a touch device and I want to actually use my left-index finger, or a stylus (a la Nintendo DS, et al). This is not a hard problem to solve generically, but it is rarely solved in my experience. I agree with what you're saying, the problem I see is that OP has pointed out _why_ this feature is required (accessibility) but 5 years later it's still not solved. This is frustrating as the person that _needs_ that feature. If any one of those developers had _needed_ the feature, I bet it'd have been implemented in no time at all. The people responsible aren't affected, and thus don't care. When your user-base is as large as Google's, a small feature like this might affect more people in that tiny minority that the entire customer base of some small companies, but at this scale they're so far removed, nobody cares. Talking of features we want Google to add; when are they going to finally allow us to set the hostname on Android phones? I'm sure that one was opened half a decade or so ago (This one issue is now 9 years old: https://issuetracker.google.com/issues/36912590 https://issuetracker.google.com/issues/36912590)
- pgeorgi 8y ago
  > If any one of those developers had _needed_ the feature, I bet it'd have been implemented in no time at all. The ticket the blog author refers to was opened by someone @google.com. There are at least 5 different additional @google.com addresses chiming in in favor of such a feature. Even when developers want something, they don't always get it on the schedule they desire.

alias_neo 8y ago

My example isn't the greatest, I agree, because it is, generally supported everywhere. A more appropriate example might have been scroll-bars, very few devices support moving them to the left. particularly when it's a touch device and I want to actually use my left-index finger, or a stylus (a la Nintendo DS, et al). This is not a hard problem to solve generically, but it is rarely solved in my experience. I agree with what you're saying, the problem I see is that OP has pointed out _why_ this feature is required (accessibility) but 5 years later it's still not solved. This is frustrating as the person that _needs_ that feature. If any one of those developers had _needed_ the feature, I bet it'd have been implemented in no time at all. The people responsible aren't affected, and thus don't care. When your user-base is as large as Google's, a small feature like this might affect more people in that tiny minority that the entire customer base of some small companies, but at this scale they're so far removed, nobody cares. Talking of features we want Google to add; when are they going to finally allow us to set the hostname on Android phones? I'm sure that one was opened half a decade or so ago (This one issue is now 9 years old: https://issuetracker.google.com/issues/36912590 https://issuetracker.google.com/issues/36912590)

pgeorgi 8y ago
> If any one of those developers had _needed_ the feature, I bet it'd have been implemented in no time at all. The ticket the blog author refers to was opened by someone @google.com. There are at least 5 different additional @google.com addresses chiming in in favor of such a feature. Even when developers want something, they don't always get it on the schedule they desire.