gagslondon
Programmer
I have searched for this because I am sure MX's idiosyncrasies have been discussed here already but I have not found any refernce to the problem I encountered today.
I am teaching actionscript at the moment and my class is full of bright people but with no experience of Flash. So mistake one is putting code where it shouldn't go.
Obvious mistake and one that everyone makes. The problems I am having is that when I have isoloated the code and got the student to attach it to a clip instead of on a frame Flash still kicks out errors for the now non-exitstant code on a frame somewhere.
Deleting the layer doesn't work, I even copied and pasted the object onto a new movie and the bug came with it!!!
Anyone else come across this? It is a right pain to try and teach with this bug (as is properties not being green anymore) and I am stumped to what to suggest to my class.
I am pretty certain this happens on both pc's and macs.
This is enough for me to not use MX really.
Any ideas? (or a good excuse or two) !!
cheers
g
I am teaching actionscript at the moment and my class is full of bright people but with no experience of Flash. So mistake one is putting code where it shouldn't go.
Obvious mistake and one that everyone makes. The problems I am having is that when I have isoloated the code and got the student to attach it to a clip instead of on a frame Flash still kicks out errors for the now non-exitstant code on a frame somewhere.
Deleting the layer doesn't work, I even copied and pasted the object onto a new movie and the bug came with it!!!
Anyone else come across this? It is a right pain to try and teach with this bug (as is properties not being green anymore) and I am stumped to what to suggest to my class.
I am pretty certain this happens on both pc's and macs.
This is enough for me to not use MX really.
Any ideas? (or a good excuse or two) !!
cheers
g