Limit or Check on object movements over 100m?

Having just accidently sent another concrete slab skyward by editing it's Z position wrong, I would like to propose we have an "Are you really sure?" box or movement distance limit placed on objects for say if you ever try to edit them into a new position over 100m from their current position, maybe 50m?
So please wear a hardhat if you are pasing through Desire sim today
If you don't want either just vote No Limit and No Warning, if you don't care whether it's either just vote a distance
I guess the warning is better for people wanting to throw a skybox up to 700m in one click

drink more coffee first

I wish it were that simple to stop stuffing up

If you uncheck "Limit Select Distance" in the Client/Advanced menu the selection should remain after you send a prim flying, Ctrl-Z (Edit / Undo) will bring it right back in that case .

Thanks Kitty, that sorta sunk the whole concept by having an existing fix for it

Should have actually tried it again before suggesting .

It doesn't seem to still work, or when it does it's rather unreliable .

I think that the warning/limit should only come up if the user has Limit Select Distance enabled and that if the movement is over 100m then warn, also possibly warn if the movement is over 50 and that the move would take the object out of select range.

Makes sense then it could be a checkbox so all could be happy, I finally found my missing concrete slab at 751m instead of 75.1m Altitude

I posted a JIRA issue for such a feature a while ago, and LL closed it saying they'd rather have a better undo feature. Guess what, we still have neither!

I'd re-open it but the JIRA is broken half the time I look at it, and this is precisely such a time.

The proposal I made was for an adjustable limit, or a checkbox, so you can still do big movements if you want, but 99% of the time you'd leave it checked since you don't want to send your prim flying.

Heh. There is one other option, for those cases where "undo" just won't do it. Mind you, if "deselecting" and object was an action that could be undone, that would help a lot, but... How about a method of selecting objects by tabbing through them, or something similar. So, if you do deselect something you can get it back, without having to fly to find it. lol

Still, a "undo deselect" would be **far** better.