I was moving some of my code blocks around and accidentally ended up with a "Add a Copy of Object" command inside the objects itself. Ended up crashing my browser when I tried to render it (didn't lose anything though). It might be a good idea to dis-allow an object to make a copy of itself OR at least make sure that a recursive algorithm continues to monitor the maximum primitives count.
Date
Votes
3 comments
-
Wayne Losey Official comment Yes, it can be easy to run into recursions.
We are still working on core workflows, so it's not likely we will get to error behaviors in the near term. But we agree that it will help kids to debug and it is DEFINITELY on our backlog.
One simple recommendation for keeping things simple is to reduce the number of Group blocks you use. This will help you to stay below the primitive limit. In this case you can substitute the 'Select all in group' if you need to move or manipulate multiple shapes inside an Object.
-
Wayne Losey Yes. This definitely freezes the workspace.
We haven't gotten to a point of messaging an erroneous move yet, but avoiding it altogether could be beneficial.
-
Michael Peters I am using Codeblocks with classes of Grade 6s and 7s with limited coding background, so there is quite a lot of experimentation (or mucking about, depending on your perspective), and I am finding that the workspace is freezing/crashing quite often with stuff like this. Also by exceeding the limit on primitives by some enormous number by nesting loops inside each other, or whatever. So I'd like to see some more bullet-proofing and clear error messages to help me help them.
Great stuff so far though! I'm hoping for some lovely 3D printed geometric code art for my school Maker Faire!
Please sign in to leave a comment.