On 3/29/2010 19:34, Paul Louden wrote:
On 3/29/2010 6:19 PM, Jeff Goode wrote:
It is an optional feature, same as many others. If a knowledgeable
developer wants to switch it on for his target of choice, I've made
it very easy to do so. At the same time, my patch consumes no
resources and changes nothing if it isn't switched on. That, I
think, is as far as I need go.
The general expectation is that when possible a new feature should be
enabled for all targets that can support it.
If we get into the habit of just enabling features for one target each
and make no effort whatsoever, then you'll start to have a wide spread
of features across targets.
The problem is *I don't know* which targets can support it. It's a key
mapping issue, which by definition is target specific. Some targets
have color screens, some have scrollwheels, etc. Some have free ekys
and some do not. It will be up to individuals who want the feature for
a given target to implement it for that target.
