Yesterday I forgot to write a blog post so here is what happened:
I had to leave class early to perform at a Seniors home. So, Mr. Arkin gave me back my unit test from yesterday.
Today when I went to class I realized that I didn't sign the test. I didn't check the daily log, either unfortunately. I will get the notes about parameters and executables from a friend tonight.
It turns out that the class was assigned to create a program that asks for a character from the user, and outputs the character moving around the screen and "bounces" when it hits the edge of the run window.
Mr. Arkin gave us the majority of the time in class to work on the assignment. My goodness, may I say it was a challenge to get the program to work the way I want it to. I first tried writing the program using trial and error and constant mental desk checking. When something didn't turn out the way I wanted it to, I would use the debugger menu option to see why. However, even with that I wasn't able to write a program that met the criteria (hints) that Mr. Arkin revealed on Wikispaces. To restate them: (1) 34 lines long (6 of which were regarding the sound, so in reality 28), (2) one loop.
Then, I tried writing the instructions in English first. It may have been because I was doing it wrong, but I found it even more challenging and complicated. So, I finally tried drawing out what is executed in the run window. It helped me understand what had to be incremented and decremented. Before I was able to finish, class was over.
When I got home, I did some of my French homework. Then, I started working on assignment. My program worked half way, then the pathway of the character (ball) changed and was stuck. Finally, after much struggle, the program was complete using only one loop. Hurrah! And it actually works!