StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8790920
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-01-09T15:37:59.353
FavoriteCount
0
LastActivityDate
2012-01-09T15:37:59.353
LastEditDate
LastEditorUserId
0
OwnerUserId
666402
ParentId
8790178
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
To really answer this, we still need a bit more information about the format of your data and how you're applying transformations. But here's a guess: Your objects are most likely represented as collection of polygons which are themselves represented as a collection of points relative to some 'root point' such as the center of the object or a bottom corner. When you place the object somewhere, like a room, you can do so by applying a sequence of matrix multiplications to the points that represent the object. A single matrix multiply can usually do the whole transformation, but it makes more sense to us if we compose a sequence of transformations that do intuitive things. For example, you would usually <ol> <li>Scale the object to be the size you want.</li> <li>Rotate the object to be oriented the way you want.</li> <li>Translate the object to be where you want.</li> </ol> All of these transformations happen relative to the 'root point' of the object and their order makes a big difference. If you translate and then scale or rotate, the scale and rotate will happen relative to the newly translated center. So, if you have placed objects in a room, and [0,0,0] of your coordinate system happens to be in the center of the room, if you scale all of the transformed points of those objects, they will all grow/shrink and push outward/inward from [0,0,0]. Since that's not what you want, you must first change the origin by translating the object, then scale, then change the origin back to where it was. If I have two points: [3,0,0] and [4,0,0] and I want to scale them so that the distance between them is 2 instead of 1, if I just multiply (scale) by 2, I get [6,0,0] and [8,0,0]. There's a distance of 2 between them now, but they both moved. If I want the first point to stay put, then I first translate by [-3,0,0], then I scale by 2, then I translate by [3,0,0] and I have what I wanted. If, instead, I want the center of those two points to remain the same, then I translate by [(+/-)3.5,0,0]. It falls on you to decide which points of the objects should not move. Then you move that point to the origin before scaling. Then you move it back afterward. Since you don't want your objects to push through the floor, you'll probably pick a point on the ground (or whatever surface they're attached to). If you have one object resting on another (books on a desk) then those objects should probably use the same reference point. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORelatively scale an object collection in 3D space
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJCooper
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COThanks for taking the time to explain the transformation process to me!
 singulars
 PostPostId
 PO
 UserUserId
 USshadeMe

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.