In normal mode, clicking a block triggers the execution of the script containing the block. However, this may lead to unwanted behavior while in debug mode.
-
when copy-pasting a (sub)script, the click event when releasing (pasting) a copied (sub)script into an existing script, will also execute that script; this is unwanted if execution was pauzed halfway the script, so we should at least avoid that this click action also executes the script (may this is also what we want in normal mode)
-
execution a variable/expression as a separate script, executes the expressions and displays the return value
this would be a nice feature to have when execution is pauzed in debug mode, but
- clicking a variable/expression that is embedded in a script will execute the entire script, not the variable/expression in isolation
- creating a new script on the flow with only the variable/expression will clear the recorded history
both option lead to unwanted behavior; so maybe we could no longer execute the script when a block from the script is clicked, and instead evaluate the variable/expression if the clicked block is a variable/expression embedded in a larger script; maybe we still want to provide the option to execute a script either by clicking a hat block (not the other blocks of the script) or by putting this as an option in the context menu of the blocks
In normal mode, clicking a block triggers the execution of the script containing the block. However, this may lead to unwanted behavior while in debug mode.
when copy-pasting a (sub)script, the click event when releasing (pasting) a copied (sub)script into an existing script, will also execute that script; this is unwanted if execution was pauzed halfway the script, so we should at least avoid that this click action also executes the script (may this is also what we want in normal mode)
execution a variable/expression as a separate script, executes the expressions and displays the return value
this would be a nice feature to have when execution is pauzed in debug mode, but
both option lead to unwanted behavior; so maybe we could no longer execute the script when a block from the script is clicked, and instead evaluate the variable/expression if the clicked block is a variable/expression embedded in a larger script; maybe we still want to provide the option to execute a script either by clicking a hat block (not the other blocks of the script) or by putting this as an option in the context menu of the blocks