|
@Grace Hapenny: I can see the reasoning behind the request. We make many decisions based on the same criteria: what support load does this change add or remove? What this means is that from our point of view any change must not affect existing users, must not overly complicate settings, must make sense, and finally must be implementable in reasonable time.
There are many users like kaufman who use more than one connection method. In fact I would guess that many use all three and that the majority use at least two. Because of this, changing the connect button from a menu to an action isn't something I want to do.
However, I am very willing to consider something similar to what kaufman suggests: hiding or disabling connection types. This is implementable because the underlying behavior of the connect button stays the same. It is supportable for the same reason. It makes sense given that CC already has similar features. Finally, I think it mostly solves your problem because your relative would tap connect and then have only one choice of what to tap next.
Comments?
|