b12194, on Windows
Pick a block that accepts a text or number, and type in values for them. In my test I used the draw block for plain text and to draw [10 + 10]. When testing the game, both the text and the result number will draw accordingly.
Place attributes over the typed fields and then remove them. The old text and numbers will stil be there.
If you try to compile, you'll get an error because of the block for [10 + 10]. If you remove the block and try again with only the text, it will draw empty text.
When placing and removing an attribute block, or any other block that would fit the field, the text will remain in the behavior workspace, but they will actually be empty. Reloading the behavior shows empty fields on those blocks.
I expect that removing a block will revert to the typed-in values as long as the behavior wasn't closed, in case a block was placed by mistake. The issue is that it shows the old value, but the block fields are actually empty.
Pick a block that accepts a text or number, and type in values for them. In my test I used the draw block for plain text and to draw [10 + 10]. When testing the game, both the text and the result number will draw accordingly.
Place attributes over the typed fields and then remove them. The old text and numbers will stil be there.
If you try to compile, you'll get an error because of the block for [10 + 10]. If you remove the block and try again with only the text, it will draw empty text.
When placing and removing an attribute block, or any other block that would fit the field, the text will remain in the behavior workspace, but they will actually be empty. Reloading the behavior shows empty fields on those blocks.
I expect that removing a block will revert to the typed-in values as long as the behavior wasn't closed, in case a block was placed by mistake. The issue is that it shows the old value, but the block fields are actually empty.
