Qarl Linden has indicated that new scripting API for touch position will be out soon.
It all started with my forum post back in 2004 - Touch position already known, please expose it - essentially it's me asking for llDetectedTouchPos().
I've had many conversations with residents and Lindens trying to promote the idea and even a trip to San Francisco where I spoke directly with Lindens about this desired feature.
I'd almost given up on it, till Qarl wrote these magic words in the JIRA (SVC-1902): "yes - i'm happy to report that our branch has passed QA and is in the 1.21 viewer. i believe the first RC of 1.21 is coming in the next two weeks.".
If it meets all that is proposed on the LSL Touch Position wiki page then I'll be over the moon with joy.
So, let's back up a moment here. What's so special about llDetectedTouchPos() you may ask? Well, perhaps it's best to talk about the ideas. How about a single prim vendor with many buttons on it. Imagine a TV screen (SLCN.tv, get ready to update your lovely TV sets!) with channel selection menus etc, all done on one prim. Imagine the sex toys - "ooh, touch me there" kind of thing. Imagine security devices with no fingerprinting which prims you clicked in what order. Imagine single prim HUDs. Imagine prim browser operation using server side image map (it'll be slightly more complex than that, but yeah, I can imagine it). Imagine fully-functional aircraft dashboards with hundreds of buttons on them - and only one prim for the dashboard.
See what I mean? This single function creates an entire economy!
So, thank you Lindens for listening and acting. Four years is a long time for anyone to wait, glad the wait is nearly over.
Currently rated 5.0 by 5 people
- Currently 5/5 Stars.
- 1
- 2
- 3
- 4
- 5