Discussions

Thank you davmac, that explains it perfectly! My first actor's, a1, act() is lengthy, including multiple image swaps and directional changes with small wait times. I am new to programming and have decided to learn with Greenfoot. You hear all these ads about Windows machines being able to truly multi-tast so I wasn't sure if both acts were suppose to run simultaneously or if they ran in turn like you've described. Knowing they run in turn tells me it is my code and I'm trying to do too much at once. Also, thank you Duta, it is a lot like the crab scenario. In fact, the crab was my st

Short answer: You can't (as of the current greenfoot version) - you may want to look into getting a different IDE.

Ok, I have managed to reproduce the problem on Windows (not on linux though - it seems to work fine for me on linux). I'll look into it further; maybe it's a Greenfoot bug. In the meantime you can probably avoid it by not using inner types.

so now i have convertet it to a !!!GIF!!!! and it work fine... i use http://www.greenfoot.org/scenarios/260 to use the gif... now there is a loop. so i need to remove tha actor after it hast finished. to do that is shuld use a timer or something. the gif is 21 seconds ... how i make a timer????

Or of course you can just click the "code" button underneath the box you type your message in and it'll do the tagging for you :)

Wow, so at the far right (100) it's doing (or attempting to) do 40 thousand frames per second? Jesus. :L Alright, was just wondering because I was thinking of making myself a better way of timing where you could actually input a seconds value and with some calculations it would... well never mind, I can't be asked dealing with that atm >.< Thanks though, that was interesting.

Thanks for the reply!

Well, here's a very basic way of doing it: <Code Omitted>After you have put that code in, you could do something like:

Actually, it has to do with the fact that myKey can be null and most probably will be the first time this statement is reached. Instead of checking to see if myKey equals 'space' , check to see if 'space' equals myKey. Since 'space' is never null, you will avoid the null pointer exception.