I believe this happens for SPY in general, but it's definitely happening working with JS.
1) Compiler won't convert the image code to text within instructions or hint
2) After dropping block into workspace, it does not generate another line at the end of the program, making it hard to add the next block
3) After dropping a block into workspace, cursor ends up at random point in line, so if user presses enter to make a new line, they will likely split the text they just added
4) //@hide doesn't seem to work in JS
5) blockconfig doesn't seem to work in JS
6) The cursor doesn't automatically snap to the first/indented space while you're dragging, so sometimes you have to drag the block to the left outside of the workspace to get the text to appear at the beginning of the line
7) Controller block says move [mySprite] with buttons but when you drop it, mySprite becomes null
8) The JS that comes from the overlap block:
sprites.onOverlap(SpriteKind.Player, SpriteKind.Player, function(sprite: Sprite, otherSprite: Sprite) {}
Is different than the JS we typically use:
sprites.onOverlap(SpriteKind.Player, SpriteKind.Player, function(sprite, otherSprite) {}
kiki-lee
commented
4 months ago
I believe this happens for SPY in general, but it's definitely happening working with JS.
1) Compiler won't convert the image code to text within instructions or hint 2) After dropping block into workspace, it does not generate another line at the end of the program, making it hard to add the next block 3) After dropping a block into workspace, cursor ends up at random point in line, so if user presses enter to make a new line, they will likely split the text they just added 4) //@hide doesn't seem to work in JS 5) blockconfig doesn't seem to work in JS 6) The cursor doesn't automatically snap to the first/indented space while you're dragging, so sometimes you have to drag the block to the left outside of the workspace to get the text to appear at the beginning of the line 7) Controller block says
move [mySprite] with buttonsbut when you drop it, mySprite becomes null 8) The JS that comes from the overlap block:sprites.onOverlap(SpriteKind.Player, SpriteKind.Player, function(sprite: Sprite, otherSprite: Sprite) {}Is different than the JS we typically use:sprites.onOverlap(SpriteKind.Player, SpriteKind.Player, function(sprite, otherSprite) {}