However, a black key should not be created when an empty string is encountered in the loop within the 'displayKeys' method. Since Greenfoot 3.0. I am currently using version 2.4.2 as i am unable to receive any newer updates on my computer. when i try to add sound to my title screen the greenfoot debugger keeps popping up and i have no idea why. background - the color of the image behind the text. Hi Im new to programing in general, i understand the concepts of it, and Im working on a game for class. Since Greenfoot 3.0.4, passing null will use black. Adding blanks in the toggledBlack array will help to even out the arrays. Parameters: string - the string to be drawn size - the requested height in pixels of each line of text (the actual height may be different by a pixel or so) foreground - the color of the text. With the blank spaces in the arrays you are creating keys with the keyName not being equal to an existing key in Greenfoot.The blanks (empty strings) are place holders for where there is no black key on the piano keyboard. In the Key class you can't ckeck to see if a key is down if that key ('') doesn't exist. Just like you didn't for all the other keys on the board.Įven if you do add in spaces into the array, you will still get errors, just in a different class. Note that if you already have a previous version of Greenfoot installed, you will need to uninstall it first - go to the Control Panel and then 'Programs and Features' to uninstall Greenfoot. It happens to be that on a computer keyboard, the letter 'R' lies between the letters 'E' and 'T', but that doesn't mean you have to give it a blank index in an array. Instead of adding blanks into the toggledBlack array, the blanks in the other arrays should be removed. Easily Customizable Many parts of Geany are heavily customizable like color themes (Geany Themes) or adding. Yehuda wrote.I'm not sure what the purpose of all the blank array parts are for. sound files, CD-ROM control, etc.) 3D Perspective. In my computer science class at school, Greenfoot throws weird exceptions that have nothing to do with my code but I am not sure if that is the case this time.

I triple checked and I am 99% sure that I did nothing wrong. Key key = new Key(blackKeys, blackNotes + '.wav', 'black', toggledBlack) Key key = new Key(whiteKeys, whiteNotes + '.wav', 'white', toggledWhite) ĪddObject (key, 54 + (i*key.getImage().getWidth()), 140) The catch is that in your case you have to know about the collision before the collision happens. isTouching(Tree.class) checks whether the actor collided with a tree. Public Key(String keyName, String soundFile, String keyType, String toggle) Greenfoot already provides methods to check whether a collision happened, e.g. Import greenfoot.* // (World, Actor, GreenfootImage, and Greenfoot)

Adding sound greenfoot