Difference between revisions of "Talk:Touch Coordinates"
Jump to navigation
Jump to search
Gigs Taggart (talk | contribs) m (Talk:Feature Request Touch Coordinates moved to Talk:Touch Coordinates: redundant category in name) |
|||
| Line 4: | Line 4: | ||
No problem with that, just as long as it's persistent through size changes to relief the script of having to get texture size, offset, prim size and all that and calculate the button positions dynamically all the time. | No problem with that, just as long as it's persistent through size changes to relief the script of having to get texture size, offset, prim size and all that and calculate the button positions dynamically all the time. | ||
--[[User:Fairlight Lake|Fairlight Lake]] 19:10, 26 January 2007 (CET) | --[[User:Fairlight Lake|Fairlight Lake]] 19:10, 26 January 2007 (CET) | ||
Sure, UVs are normally done ranging 0-1. For the default texture mapping on a cube, the returned result would be identical for face coordinates as in the proposal, and for texture coordinates. | |||
--[[User:Moshe Sapwood|Moshe Sapwood]] 08:30, 28 January 2007 (PST) | |||
Revision as of 08:30, 28 January 2007
Might be better implemented as providing the texture U and V. This would keep code simple when a texture spans a few surfaces, and would make the use more clear with spheres, tori, etc. --Moshe Sapwood 09:31, 26 January 2007 (PST)
No problem with that, just as long as it's persistent through size changes to relief the script of having to get texture size, offset, prim size and all that and calculate the button positions dynamically all the time. --Fairlight Lake 19:10, 26 January 2007 (CET)
Sure, UVs are normally done ranging 0-1. For the default texture mapping on a cube, the returned result would be identical for face coordinates as in the proposal, and for texture coordinates. --Moshe Sapwood 08:30, 28 January 2007 (PST)