Hi, I've found a way of triggering a similar (maybe the same) error. The steps to reproduce are:
1. Create a new variable named "foo".
2. Create a new script named "foo" that assigns something to the variable.
3. Add a parameter to the script.
4. Create another script named "foo" (it will be automatically renamed to "foo1"). Make this script call the previous "foo" script.
5. Rename variable to "foo1".
6. Boom! :)
Now this is very strange, I don't know why, but after I recompiled ModifyVariableDialogMorph>>#doAccept (without making any changes to the code), the error just went away.
Cheers,
Richo
On Mon, Nov 26, 2012 at 4:21 PM, Markus Schlager
<m.slg@gmx.de> wrote:
Thank you, Bert. I'll try what you're proposing.
On Mon, 26 Nov 2012, Bert Freudenberg wrote:
It would be interesting to know what exactly happened - seems to be an unfortunate mix of textual and tile scripts with and without arguments having the same name as some variables that were added / removed in a way to confuse the system.
There weren't any textual scripts involved. The students are doing tile-scripting only. Having variables and scripts with the same names is a typical mistake among them.
Markus
_______________________________________________
etoys-dev mailing list
etoys-dev@squeakland.org
http://lists.squeakland.org/mailman/listinfo/etoys-dev