Tuesday, March 8, 2011

week 10 E

My presentation went pretty much as planned. I knew people wouldn't like the direction the project took, but at least it has a direction, a solid direction that has a well defined audience. However, after discussing it with the class, I have decided to take a more middle road with it and let the player decide between two paths to cancer redemption.

week 10 D

I couldn't remove the vomit experience because listeners were running on the particles. I couldn't turn them off with internal script because the script can't talk to each other. I'm seeing the benefits of externalizing the script, now. After wrestling with it, I just threw in a delay timer that allowed the particles to self terminate.

week 10 C

The keyboard listeners in the pill-taking experience wouldn't add to the stage because it couldn't find the stage. I figured the RAM was slowing down, since this one was farther back in the queue. The guess must have been good because adding the listeners after a short delay worked splendidly.

week 10 B

I was getting a strange error from the lumpectomy. It kept on reloading after it was finished, which would freeze the code. The reason was that the code for any following frames was duplicated off of this one, for some reason. All I had to do was erase the extra line of code on each frame.

week 10 A

Even after the files were loading, I had a problem with their unloading. At least, I thought I had a problem with their unloading. The files would unload upon self removal. The real problem was that they couldn't pass control back to the parent. The parent couldn't ask the child if it was finished, and the child couldn't tell the parent if that it was finished. No information could be passed to the other. They probably could have, if the script was external. It's internal, however. The only solutions I could come up with were: A] externalize all the scripts, which would have required rewriting the entire project; B] call the parent from the child and jumping to the appropriate frame, which would kill the RAM; or C] check to see if the child is on the stage. 'C' sounds good. I was able get the parent to ask the child what it's index is. Unfortunately, it doesn't pass -1 if not present. Instead, it throws an error. Fortunately, I can still use the error to check this.