- The lack of lists & multi-dimensional arrays
Why: That should be self evident. This is a significant limitation when the work around requires the use of HS objects just to hold data and their associated overhead causes projects with too many “data objects” to lag. Even beginners would quickly grasp the concept of lists (and arguably should be exposed to them).
- The lack of troubleshooting capabilities. E.g., being able to step into or break & step through the code to follow/understand the code sequence and watch how variables/traits change.
Why: Setting an object’s text to watch a variable is only mildly helpful as it’s only updated at one discrete time per frame & the execution can’t be paused to view momentary changes). This is the reason I never finished the Rubik’s Cube project Also, most HSers don’t understand the intra-frame code flow, so this would be a huge help to everyone.
- The inability to reuse code between projects. At least make it so code can be copied if you are the original author of the project where the copy is initiated. (I understand this isn’t as simple as it seems due to the structure of the json data, but it’s certainly technically feasible)
Why: Again, that should be self evident. No one wants to waste time recreating code, especially when it contains long arduous formulas. This would also allow the use of smaller test projects to work out a particular section of code in simpler project & then move it to the larger more complicated project.
I cancelled my subscription due to frustrations with the app & community, but I would likely return and once again encourage my kids to use Hopscotch if these improvements were implemented.