Difference between revisions of "Talk:LSL Touch Position"
Jump to navigation
Jump to search
Ina Centaur (talk | contribs) |
|||
| Line 1: | Line 1: | ||
== FAQ == | == FAQ == | ||
Will this feature have seamless deprecation... i.e., will HUD's using these new touch features break on older viewers? ([[User:Ina Centaur|Ina Centaur]] 04:17, 26 July 2008 (PDT)) | Will this feature have seamless deprecation... i.e., will HUD's using these new touch features break on older viewers? ([[User:Ina Centaur|Ina Centaur]] 04:17, 26 July 2008 (PDT)) | ||
:Yeah, it's dependent on the viewer version. The return values do let you check for support, so you can offer a pre-purchase test or switch to an alternative interface or something like that. -[[User:Viktoria Dovgal|Tori]] 13:39, 8 August 2008 (PDT) | |||
== ETA == | == ETA == | ||
- When will the implementation be standardized on regular viewers? | - When will the implementation be standardized on regular viewers? | ||
Revision as of 13:39, 8 August 2008
FAQ
Will this feature have seamless deprecation... i.e., will HUD's using these new touch features break on older viewers? (Ina Centaur 04:17, 26 July 2008 (PDT))
- Yeah, it's dependent on the viewer version. The return values do let you check for support, so you can offer a pre-purchase test or switch to an alternative interface or something like that. -Tori 13:39, 8 August 2008 (PDT)
ETA
- When will the implementation be standardized on regular viewers?
Tangential new feature requests
- To minimize the need to upload composited UI image's from multiple textures stitched together (once displayed on several prims, now displayed on a single prim), the ability to display multiple textures on a single prim surface (without primtorturing a prim). Ex llSetTextureBoundaries(key textureName,list boundaries) (Ina Centaur 04:04, 26 July 2008 (PDT))