STCC-156-227 distanceTo- and glideTo-bricks #170
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sandra0521
approved these changes
Apr 29, 2020
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
STCC-227: using the sensing brick for distance resulted in a crash when the mouse-pointer was the target, that is now fixed by replacing the outdated catroid code with the currently used one; additionally some test-cases for this type of conversion were added (previously non existent)
STCC-156: workaround for 'glideTo'-brick with the following objects as target: random position, any other sprite and mouse-pointer (workaround similar to the 'distanceTo'-workaround); added test-cases for this types of conversion