If you did not use Font or Color in your scenario then nothing will need to be changed (Greenfoot will still ask if you want to automatically convert the scenario, but it won't find anything to convert.) If you were using Font or Color, you probably had an import statement at the top of your class like: This should be sufficient in 90% of cases read on for details on what you need to do if the automatic conversion isn't enough, or if you need to use the scenario with an older version of Greenfoot again in future. The easiest thing to do is to say yes and let Greenfoot do the conversion.
When you load a scenario edited with Greenfoot version 3.0.4 or earlier in the new 3.1.0 or later, it will ask if you want to automatically convert your scenario to use the new classes. Normally you do not need to separately import them: Most Greenfoot scenarios use an import statement of the form In all future scenarios, please use these classes in preference of the awt classes. The Greenfoot library now has two new classes, greenfoot.Color and greenfoot.Font, to replace use of and. We decided to change the API to supply our own classes to improve future flexibility. These are part of the Java desktop API, and using them was hampering potential future work to get Greenfoot running in a wider variety of settings. In Greenfoot 3.0.4 and earlier, the Greenfoot API used the and classes.
0 kommentar(er)
