If you want to make your sprite reusable(which is a very good thing), then follow this guideline:
1.Name of your sprite should be rather unique. "sprite1" is not a good name.
2.Your sprite should never use the "forever" block, use "repeat until" instead.
3.Use as few global variable as possible. Use "broadcast" and "when I receive instead". (messages should be unique)
4.If you have to use some global variable, give them very unique names. "score", "a", "x" are bad names.
5.Try to eliminate unnecessary threads such as "when space pressed...".
6.If there's color collision detection in your program, make the color rather unique.
That's all I got so far, feel free to add more to it.
Offline
I've had trouble exporting sprites from one project and importing them into another.
I had designed my print_decimal and one-sprite-composer programs especially to be sprites that were reusable, but I've only been able to reuse them by importing the whole project. Importing just the sprite seems to get a sprite that looks ok, but whose scripts don't run---as if the symbol table for the variables had been messed up by the import.
Offline
Yes, there were three global variables, and it did seem to be the global variables that were messed up. The globals were used as "parameters" for passing information to the sprite, so there is no way to avoid them. Importing the whole project got the variables properly, so I think it is a bug in the sprite import/export involving additions to the symbol table.
Offline
Hi all,
Thanks for this bug report. I tried to replicate it by exporting and then importing a sprite with global variables, but found that it worked correctly. Do you know how to replicate this problem?
Thanks,
Tammy
Offline
Create two sprites, one that writes to a set of global variables and one that reads from the global variables. If you export and then import the sprite that reads the global variables then the imported one won't read the variables correctly. I can upload an example if that doesn't help.
Offline