StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POEffective communication in a component-based system
primarykey
Id
2819923
data
AcceptedAnswerId
2820050
AnswerCount
3
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-05-12T14:50:47.227
FavoriteCount
1
LastActivityDate
2011-02-02T11:07:36.120
LastEditDate
LastEditorUserId
0
OwnerUserId
160990
ParentId
0
PostTypeId
1
Score
2
ViewCount
546
LastEditorDisplayName
text
Body
Yes, this is another question about my game engine, which is <a href="http://www.youtube.com/watch?v=XdJ6aqSx2dc" rel="nofollow noreferrer">coming along very nicely</a>, with much thanks to you guys. So, if you watched the video (or didn't), the objects in the game are composed of various components for things like position, sprites, movement, collision, sounds, health, etc. I have several message types defined for "tell" type communication between entities and components, but this only goes so far. There are plenty of times when I just need to ask for something, for example an entity's position. There are dozens of lines in my code that look like this: <pre><code>SomeComponent comp = (SomeComponent)entity.GetComponent(typeof(SomeComponent)); if (comp != null) comp.GetSomething(); </code></pre> I know this is very ugly, and I know that casting smells of improper OO design. But as complex as things are, there doesn't seem to be a better way. I could of course "hard-code" my component types and just have <pre><code>SomeComponent comp = entity.GetSomeComponent(); </code></pre> but that seems like a cop-out, and a bad one. I literally JUST REALIZED, while writing this, after having my code this way for months with no solution, that a generic will help me. <pre><code>SomeComponent comp = entity.GetComponent<SomeComponent>(); </code></pre> Amazing how that works. Anyway, this is still only a semantic improvement. My questions remain. <ol> <li>Is this actually that bad?</li> <li>What's a better alternative?</li> </ol>
Tags
<c#><design-patterns><components><messages>
Title
Effective communication in a component-based system
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USTesserex
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. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POEffective communication in a component-based system
 UserUserId
 USSoylent Graham
 VoteTypeVoteTypeId
 VTFavorite
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.