This discussion is closed: you can't post new comments.

A point of Soreness

Not that I would wish, really, to discuss points of personal soreness with the crowd; but, heaven knows, this is some sort of historical document.

It all began with a missive from Soft Linden on the subject of things which might be included in the forthcoming 1.20 Release of the Client which enables us all to view the splendid Grid. Said missive included the forthcoming:

* DEV-4706 Make running more intuitive by double-tapping forward

Now, I consider that this would be a terrible thing; not at all instantly destructive of course, but at present, double-tapping has no meaning, thus there are scripts which attempt to use it for their own purposes - my own Dragonfly Wings, that Samurai Combat Island thing, all sorts. Adding client behaviour to that would disrupt that.

Thus, I made my objections known on said List, and was immediately directed towards the fabled JIRA, with the suggestion that I make complaint regarding an issue which did not at that time exist. Well. If instructed, so I shall do, and here it is: 1.20 source - "double-tap to run" should not be implemented. A minor contribution, I am sure you will agree (though please - do vote).

In the second comment, though, one encounters the following:

I have altered the title of this Jira. You should not petition for total removal of a feature if some will find it useful (and some will). Instead, this feature should be a client option and should not be enabled by default.

The alteration referred to was to basically remove any reference to whatever the JIRA was about. So, "I should not petition for" something? Oh, dear sir, I dare say that I should and will.

Anonymous's picture
10 Apr200808:18
Linden Lab wants to break C:SI Dash, reassign keys at Daikon (not verified)

[...] today’s post, A point of Soreness, Ordinal discusses a proposed feature change from Linden Lab that will (if it is implemented as [...]

Anonymous's picture
10 Apr200810:18
Takuan Daikon (not verified)

Looks like they just released the Release Candidate viewer with this "fix" :(

Anonymous's picture
23 Apr200907:48
Anonymous (not verified)

A test comment.

Ordinal Malaprop's picture
23 Apr200908:32
Ordinal Malaprop

And another test comment.

Ordinal Malaprop's picture
23 Apr200909:06
Ordinal Malaprop

And again. I have no idea why I am abusing this particular post.

Ordinal Malaprop's picture
23 Apr200909:10
Ordinal Malaprop

And just a final one as it all seems to be working reasonably now.