Landmarks - Stop the auto-teleport

In the older releases of SL, when you double clicked a LM, it simply opened it. Now, if you double click, it wants to just TP you. It is nice enough to pop up a window asking you if you really want to -- UNTIL such time as I do something stupid like click the little checkbox telling it not to ask me anymore. Don't ask me why I checked that box - I don't have a clue.

How do I get it to ask me again? Now it just automatically sends me places when I forget and double click those damn things. I have dropped in on some interesting happenings without really meaning to.

Preferences --> Popups

From there you can choose which questions get asked and which don't.

Thanks - found it

Don't like how they buried the show-on-map option. >_<

Nor do I. In fact, I can't even think why they did that - it was handy.

Someone implemented the feature, submitted a JIRA on it, put it on the bug triage agenda and showed up to argue his case, people there thought it was handy (although I did argue against changing it) so it got accepted into the main viewer.

I can see how some would like it that way. It would have been nice if they had given us some sort of Preference setting on it, though.

I think I suggested a toggle back then (not sure, it was mid-summer when that feature was accepted ).

If they had just kept the old way but added an "Don't show this window, just tp me" checkbox on the old Landmark properties window then everyone would have been happy .

Unfortunately, there is no option in the JIRA to vote "Please, for the love of gods, DON"T DO THAT."

/me would vote to get that vote option added.

yeah, like the Linden Love machine, you can't actually say "no". Keep in mind, we don't actually "VOTE" to get a option added or changed, we only VOTE to get it noticed. There's no actual "voting for or against" going on, the current "vote" system really should be renamed "bump" or "ping" or something.

Personally I'd love it if the Lindens would let us VOTE on changes to the system. Of course, if they had, I doubt that the communicate window, or voice for that matter, would be here today.

There are comments though, and if the comment is entered before the jira gets enough attention to get on the triage agenda, it's pretty likely that some folks will read it. But that's already asking a lot of time, to keep monitoring the jira page for Very Bad Ideas(TM). And no guarantee it'll work. One can improve the odds by investing even more time watching the triage agendas to attend and plead one's case in person, but then you have to be in-world when the triage happens, and stuff on the agenda will drift from week to week without getting heard because shinier topics pop up.

Even if you have the ear of the developers, there's no guarantee they'll pay attention. (I'm thinking of Strife's attempts to prevent an especially embarrassing change of script functionality that had to be reversed after it hit the grid.)

But there are successes. An ill-conceived plan to fix group IMs in the 1.19 roadmap got squashed recently, I think through intervention of SLDev list members. (It would have been *ugly*--you don't want to know!)

So, for this one, probably a jira to recover some of the lost functionality would get support and eventually get implemented. One of my scripting jiras will be in the next release, so I know it can happen.

Right click while still in your inventory>>
about landmark>>
show on map.

Yeah i used to be in the habit of looking on map before i leap to a place....but now i open the landmark and I'm there!
Wish I could switch it off

I believe I said "buried."

I'd like to have it right there on the LM, not having to menu-dive for it.

That doesn't really (or didn't used to, haven't bothered to go to the triages in a while now) matter though.

"Feature suggestions with attached patch" get preferential treatment, and the agenda is on the public wiki anyway so you could implement your new feature and create a JIRA on it on Monday and have it be on Wednesday's agenda and accepted.

The order (or used to be) is "Bugs with attached patch", "Feature changes with attached patch", "General Bugs" and "General feature changes" so a 0 vote already implement feature change would come before a general bug with 20 votes.