Talk:Data Types: Difference between revisions
From Legacy Roblox Wiki
Jump to navigationJump to search
>NXTBoy No edit summary |
>Blocco No edit summary |
||
| Line 10: | Line 10: | ||
::: Is the nesting supposed to show composition, or inheritance? Only I'd say that [[Vector3]]s are ''derived'' from [[Vector2]]s, whereas [[UDim2]]s are ''composed'' from two [[UDim]]s. {{User:NXTBoy/sig|date=14:27, 31 May 2010 (UTC)}} | ::: Is the nesting supposed to show composition, or inheritance? Only I'd say that [[Vector3]]s are ''derived'' from [[Vector2]]s, whereas [[UDim2]]s are ''composed'' from two [[UDim]]s. {{User:NXTBoy/sig|date=14:27, 31 May 2010 (UTC)}} | ||
::::I think it's supposed to show composition. --<span style="color:#550909; border-color:#880909; border-size:1px; background-color:#dddddd;">Blocco</span>|<sup>[[:User:Blocco|Userpage]]-[[:User talk:Blocco|Talkpage]]</sup> 14:49, 31 May 2010 (UTC) | |||
Revision as of 14:49, 31 May 2010
Why would Vector2 and Vector3 be related at all? UDim2 is composed of 2 UDim values (X and Y). BrickColor has a Color3 property (Color). But Vector3 does not contain a Vector2 and Vector2 definately does not contain a Vector3. --GoldenUrg 22:15, 30 May 2010 (UTC)
I don't see any need to place these into a hierarchy. Vector3 is a basic object used for a lot of functions independent of CFrame. Nor do we need to explain CFrame here. --GoldenUrg 05:20, 31 May 2010 (UTC)
- Since when is the rotational matrix on the data type list. Its a component of CFrame, not its separate data type. I vote to remove it from the list since it is already explained on the CFrame page. --Camoy 12:04, 31 May 2010 (UTC)
