Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This is not strictly a symptom of bad design. Although you certainly could abstract the types out of the type checking. For the sake of performance and runtime customization, you should almost definitely NOT use RTTI or other direct type checking systems. Implementing your own (much simplified) type checking dynamic allows objects to define collision behavior at an object level rather than a class level and to redefine collision behavior at runtime.</p> <pre><code>//PSEUDO CODE enum CollisionTypes = {HARD_THING, SOFT_THING, EXPLODING_THING}; class FragileThing is a GameObject { public function getCollisionType() { return SOFT_THING; } public function collideWith(GameObject obj) { if (obj.getCollisionType() == SOFT_THING) print "whew..."; else print "OUCH!"; } } class CollisionDispatcher is a PhysXCollisionListener { public function getCollisionFromPhysX(Collision col) { col.left.collideWith(col.right); col.right.collideWith(col.left); } } </code></pre> <p>Another system that I have seen used (in books) is to use an engine wide messaging framework to dispatch collisions with type information embedded into the message. Unrelated types can simply ignore the messages. I have not tried this though. I would also recommend examining your LevelObject class to determine if there isn't some kind of common functionality you can add to it that would sidestep this problem. For instance, if there are very few fundamental types of objects (Red and Green perhaps, or Ethereal, Soft, Hard, Explosive) then you can, instead of conditional statements, encode those types into function calls: <code>function collideWithSomethingHard(LevelObject obj)</code> thus allowing objects to define only the collision behavior they care about. Hope this helps a little.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to find out the type of a variable, with inheritance/polymorphism involved
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USTim
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI've done something like this, thanks.
      singulars
      1. PO
      1. USxcrypt
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload