#Greenfoot world how to
#Greenfoot world code

This behaviour remains the default in Greenfoot 2.0 - but you can now configure your world to allow actors to leave the visible area for specific scenarios, should you want to do that. This has great potential of confusion and difficulty for beginners. In fact, you may not even be aware that they are still there. You cannot interact with them anymore, and you don’t really know where they are. This has good reason: if actors were to leave the visible world, it can be very hard to get them back. When they try to move beyond world boundaries they are simply placed at the edge of the world. The last bit of functionality I’ll talk about today are unbounded worlds.Īs you know (if you have used Greenfoot in the past), actors cannot leave the world. When images are created, they are automatically placed into the scenario’s images folder, so that they are immediately available for use in Greenfoot.

#Greenfoot world how to

(I will write in more detail about some of these new functions in separate posts soon – I’ll discuss how to do this then.) This behaviour can also be configured to select a specific application. By default, Greenfoot will open the default application for the chosen file type on any platform. This will happen in external applications. The action menu under the image list offers functions to edit, delete or create an image.

#Greenfoot world code

As some of you had discovered before, the code for the debugger has been there under the hood for some time (and there were ways to make it come up), but it was not working well, not supported, not finished, and had no proper interface. But if you need more sophisticated functionality, create a GreenfootSound object and you can control the sound in more detail. This makes working with sounds much more flexible.įor short, simple sounds (such as sound effects), the aySound(…) method is still the best to be used. It has method for starting, stopping and pausing sounds, as well as looping. Now, Greenfoot has a new class called GreenfootSound. In previous Greenfoot versions, programmers had little control over how sounds are played. So go on and write your first MP3 player. Yes, mp3 support! Greenfoot can now play mp3 files! Really. You now also have more control over sound playback. It works, however, with most microphones, and we hope that the remaining problems will be fixed in a future Java update.īut sound recording is not all that’s new with sound. There is unfortunately a Java bug that cases problems with sound recording on some USB connected microphones. However, the built-in recorder should be sufficient in many cases. If you want more sophisticated sound editing, you can still use third party applications (such as Audacity). The functionality is very simple - just recording and trimming is supported - but this is what you need most of the time.

It can be found in the Controls menu, and you can now record your sounds directly from within Greenfoot. Greenfoot now has a built-in sound recorder. Right-clicking the world itself (or indeed the grey background behind it) will show the world object context menu and lets you invoke the world methods. We have now removed this name, and instead made the whole world area right-clickable.

It had, in fact, almost easter egg-like quality. It was bad UI design, since nothing in the name indicated that this was clickable. The problem was that this functionality was quite hidden, and many users never discovered it. It had a right-click functionality, that let you access the world object’s context menu to invoke instance methods on the world object itself. The name of the world used to serve as a placeholder to represent the world object itself. Sharp-eyed users may notice one small change: the world name, that used to be shown above the world in the main window, is not there anymore. “Where’s the new stuff?”, I hear you ask. The Greenfoot main window looks pretty much as it used to look before. (Yes, we are now supported by the good folks at Oracle, instead of Sun Microsystems, after Sun was swallowed up by Oracle.)īut after that, it all might look rather underwhelming at first. The first thing users will notice after upgrading is a new splash screen. New features are available in the editor, for processing and recording sound, for editing images, debugging your programs, and more. Here, I will summarise the most interesting changes (at least those that users can directly see – there are many internal improvements to performance and stability that I won’t discuss here).