StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16429456
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-05-07T22:14:34.887
FavoriteCount
0
LastActivityDate
2013-05-07T22:14:34.887
LastEditDate
LastEditorUserId
0
OwnerUserId
2359802
ParentId
16428048
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
First, you have to decide whether you want your objects on the stack or the heap. Since they're objects, you probably want them on the heap, which means your 2D array will have 3 stars, and you will access the animations like this: <pre><code>hgAnimation* theSecondAnimOnTheFourthTurtle = turtleAnim[4][2]; theSecondAnimOnTheFourthTurtle->DoSomething(); </code></pre> If that's what you want, then first you make the matrix of pointers. <pre><code>hgeAnimation*** turtleAnim = new hgeAnimation**[TURTLECOUNT]; </code></pre> Then you can loop through the turtles. For each turtle, you make an array of pointers to the animations. For each element of that array, you make the animation itself. <pre><code>for (int turt=0; turt<TURTLECOUNT; ++turt) { turtleAnim[turt] = new hgeAnimation*[TURTLEANIMATIONS]; for (int ani=0; ani<TURTLEANIMATIONS; ++ani) { turtleAnim[turt][ani] = new hgeAnimation(parameter1, par2, par3); } } </code></pre> If that looks tricky, deleting all the arrays will be a pain too: <pre><code>for (int turt=0; turt<TURTLECOUNT; ++turt) { for (int ani=0; ani<TURTLEANIMATIONS; ++ani) { delete turtleAnim[turt][ani]; } delete[] turtleAnim[turt]; } delete[] turtleAnim; </code></pre> The fact that this is tricky is a good sign that there's probably a more simple way to design it. How about a turtle class that has a member like: <pre><code>class ATurtle { private: std::vector<hgeAnimation*> myAnimations; </code></pre> Then in your class's constructor, you can do whatever you want in order to make the animations. <pre><code>ATurtle::ATurtle(par1, par2, par3) { myAnimations.push_back( new hgeAnimation(par1, x, y) ); myAnimations.push_back( new hgeAnimation(par2, z, a) ); myAnimations.push_back( new hgeAnimation(par3, b, c) ); } </code></pre> That way, you can make your turtles in a single array: <pre><code>ATurtle* turtles[TURTLECOUNT]; for (int t=0; t<TURTLECOUNT; ++t) { turtles[t] = new ATurtle(par1, par2); } </code></pre> And in your turtle class, you would access the animations like so: <pre><code>(*(myAnimations.at(1)))->DoSomething(); </code></pre> or <pre><code>std::vector<hgAnimation*>::iterator i, end=myAnimations.end(); for (i=myAnimations.begin(); i!=end; ++i) { (*i)->DoSomething(); } </code></pre> You will still have to call delete on each element of your vector in this case, though, since you called new for every element. <pre><code>ATurtle::~ATurtle() { std::vector<hgAnimation*>::iterator i, end=myAnimations.end(); for (i=myAnimations.begin(); i!=end; ++i) { delete (*i); } } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POc++ Dynamic 2d array not using default constructor
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USCorey
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POc++ Dynamic 2d array not using default constructor
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

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.