Difference between revisions of "Talk:Touch Coordinates"
Jump to navigation
Jump to search
(suggest texture UV instead of surface XY position) |
|||
| Line 1: | Line 1: | ||
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. | 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. | ||
--[[User:Moshe Sapwood|Moshe Sapwood]] 09:31, 26 January 2007 (PST) | --[[User:Moshe Sapwood|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. | |||
Revision as of 10:09, 26 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.