StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17904108
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-07-28T01:24:32.773
FavoriteCount
0
LastActivityDate
2013-07-28T01:47:49.713
LastEditDate
2013-07-28T01:47:49.713
LastEditorUserId
2246674
OwnerUserId
2246674
ParentId
17903953
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
As I said in a comment, it's too hard to read. While I'm not going to claim it's the problem (use a debugger as suggested by Mitch Wheat), it sure could be addressed! First, lets outline a collision detection for a single axis, X. Instead of looking first for a collision, let's look for no collision. There isn't a collision along the X axis [only] when "(player to left of enemy) or (enemy to left of player)". (Reason that if neither of these are true then "player on enemy" must be true - use pictures if needed.) Let p = Player, e = Enemy, then there is a no collision [only] when (p.X + p.W < e.X) || (e.X + e.W < p.X). This means that there is a collision in the opposite/negated case! Thus we can write the collision method: <pre><code>bool Collides (IEntityBox p, IEntityBox e) { bool noCollisionX = (p.X + p.W < e.X) || (e.X + e.W < p.X); bool collisionX = !noCollisionX; bool noCollisionY = (p.Y + p.H < e.Y) || (e.Y + e.H < p.Y); bool collisionY = !noCollisionY; // not that the collision on BOTH axises must be fulfilled return collisionX && collisionY; } </code></pre> Notes (left as an exercise): <ol> <li>IEntityBox has X/Y and W/H properties and (0,0) is assumed to the Top-Left corner of the screen. Use the the correct types/propeties for your implementation. It's simpler if the positioning is unified between the player and other entities.</li> <li>The expressions can be rewritten (and De Morgan's can be applied) to clean it up a little bit. Simple collapsing would eliminate all variables and yet keep it "easy" to read.</li> <li>If noCollisionX (which implies !collisionX) is true, we don't need to compute noCollisionY. This could either use an if/else or short-circuit evaluation if collapsed.</li> </ol> Usage is likewise cleaned up: <pre><code>bool PlayerCollidesWithAnyEnemy () { foreach (var e in enemies) { // avoid hard-coding numbers if (Collides(player, e)) { return true; } } return false; } // .. var playerOopsed = PlayerCollidesWithAnyEnemy(); </code></pre> Or, with LINQ: <pre><code>var playerOopsed = enemies.Any(e => Collides(player, e)); </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCollision Code isn't working, despite several checks
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USuser2246674
UserOwnerUserId
1. USuser2246674
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. This table or related slice is empty.
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.