llDetectedTouch versioning question

Hi there,

I'm about to script an object that is using llDetectTouchFace and llDetectTouchUV on a prim. I found out that this will not work if I test it with the current onRez Viewer.

Are there other Viewer versions around that also don't support these new functions?

Thanks
Jim

Quite a few.

These are really "new" commands (only just released in the current 1.21 viewer)

The following is opinion.

My rule is "2 versions after a new command becomes official"

From a business perspective, I wouldn't attempt to sell a product that relied on those functions, until Viewer version 1.23 becomes official (after it ends RC). since the current RC is 1.22, it's going to be a while before 1.22 is officially released, then 1.23 goes into RC, and then 1.23 gets officially released. (the same personal rule also applies to sculpt-flipping).

Regardless of selling anything using these commands, I wouldn't deploy anything in my shop that required "customers" to be able to use them (info kiosks, etc).. and I most certainly, definitely wouldn't risk my business's sales by risking excluding a lot of my customers, were I to deploy a VENDOR based on those commands.

Now is a great time to play in sandboxes, learn how to use them, get comfortable using them.. designing new products.. and let OTHER PEOPLE make these kinds of mistakes. let THEM take chances and ride the razor's edge. And in 3-6 months, when 1.23 is out (I'm just guessing on that).. then MOST of the old "nicholaz" users will finally have upgraded because sculpt-flips don't work for them, and they keep running into llDetectedTouch things (As an example, people using versions 1.19 and below are in the extreme minority now.. and by now, they're clearly aware that they're "missing out" on the newer stuff).

But if you take the next couple of months to work, and watch others and see how it can be used.. you get all the benefits of getting your competition to give YOU design ideas, meanwhile you won't have to take the complaints from angry customers on an old viewer, who can't get it to work.

great advise, thanks a lot

Jim

Winter gave great advice, but I prefer to go one step futher. I don't hold off a product for 6 months, in fact I have already released several products that requier touch functions, but I do include an alternative access method, normaly an llDialog() style menu.
If the detectedTouch functions return an invalid result, I send the user an IM stating that they need a newer browser version and then present the Dialog interface so they may continue useing the object the less efficiant way.

hey, you must have read my mind

that's exactly what I had in mind, to send my object to a fallback state that will just implement the alternate behaviour.

Jim