You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think I have raised this before, but the current approach is deeply disturbing in terms of teaching computational thinking.
Unattached blocs function as if they were attached.
This is not only poor logic, but is also contrary to apps such as Scratch.
It also prevents a very important function...
I have a stack of blocks which are not functioning correctly.
I disconnect parts of the stack to identify where the problem is.
In scratch that works. In Ottoblockly, the disconnected blocks still function, but not in the order that I would expect.
The only way to prevent them from functioning is to delete them entirely, but I don't want to have to rebuild them later.
The text was updated successfully, but these errors were encountered:
I think I have raised this before, but the current approach is deeply disturbing in terms of teaching computational thinking.
Unattached blocs function as if they were attached.
This is not only poor logic, but is also contrary to apps such as Scratch.
It also prevents a very important function...
I have a stack of blocks which are not functioning correctly.
I disconnect parts of the stack to identify where the problem is.
In scratch that works. In Ottoblockly, the disconnected blocks still function, but not in the order that I would expect.
The only way to prevent them from functioning is to delete them entirely, but I don't want to have to rebuild them later.
The text was updated successfully, but these errors were encountered: