Open benloh opened 2 years ago
We thought we might be able to just "auto-add" any missing features when using Touches, but the problem is actually rather complex.
A few gotchas:
A few rules the system should enforce:
# PROGRAM DEFINE
Costume
should always be added before Physics
Physics
should always be added before Touches
Touches
should always require both Costume
and Physics
b2b
).Would it be better for the system to:
a) quietly default to values if the user did not set them (leading to mysterious magical behaviors)
or
b) passively show help to the student so they know what they need to do and how to do it
or
c) auto-insert explicit gemscript commands to set default values so that they are visible and can be changed by the student?
Feature dependency checking for Vision is potentially even more complicated.
For example, for canSeeColorOfAgent
to work:
This is probably a 2.0 feature.
When adding touch, it appears you need to have used addFeature for Costume, then Physics, then Touches, in that order. So it’s a bit of a hassle