Skip to content

Findings of reviewing old code from 2017

ben243871694 edited this page Jul 25, 2018 · 1 revision

general ideas

should we state that we picked our collision detection algorithm from stackoverflow?

Ideas from old code Collison

  • collision groups
  • collsion handling via events (blocks)
  • the idea of a margin zone around a morph and the "touching" of morphs when the morphs do not intersect but are in each others margin zone.

similar things to our collision code

  • different collision shapes via inheritance

Collision questions

  • why all this contains methods which should check something like whether a shape completly lies inside another shape
  • what is a PasteUpMorph
  • Is it possible that a collision morph loses all its handles when it is an obstacle and then is declared as not an obstacle?