Discussions

Never mind, I figured out what I did wrong, it works all perfectly now. Thanks for everything Dan!

It was indeed not in a method, this fixed it, thank you!

thanks

Running on Windows 8.1 With GreenFoot 2.4.0. http://gyazo.com/4cf93f7ab1d255929faeedb84123a248 http://gyazo.com/3ef0c9630b111660ee12440e31776cd1 I think it is the problem. How to fix it?

One discussion on the 'getUnivX' and 'getUnivY' methods is here. It appears that is when I added the 'getScrollingWidth' and 'getScrollingHeight' methods. Anyways it does provide a use for the methods (as they were written at the beginning before this post; or, as in this discussion) and shows how they can be used.

The initial line I gave would be the least you would need; however, this would require the counter to update its image every act cycle. The second way, lines 3 and 4, is better only in that the counter only updates when needed -- that is, when the score actually changes. This reduces the workload on the system as working with multiple or large images is one of the major causes in producing lag.

You probably have a line like the following to go to the Level 2 world: <Code Omitted>That line is short for this: <Code Omitted>The expanded code gives you a reference to the new Level 2 world created. You can access any public field and execute any public method in that Level2 world right between those lines. For example: <Code Omitted>

The first solution did the trick, thank you!

Use the 'bounded' parameter to the World class constructor to specify whether you want a world to be bounded (actors contained within world bounds) or unbounded (unconstrained actors). Normally your world constructor has a line like: <Code Omitted> You need to add the 'bounded' parameter. For an unbounded world, that should be false: <Code Omitted>

Then it should work fine. You need to put the relative path to the image. If the image is called 'a.jpg' and is in folder 'abc' inside the images folder, then you name it as 'abc/a.jpg', eg: <Code Omitted>

Also 'Counter' for a field name has multiple downsides. First one thing, by convention, field names should begin with a lowercase letter. For another, the name does not remotely describe what the field is for -- you are not using it as a counter, but more as a direction indicator. Better would be to use it for the direction itself, which can be found at the end of lines 11 and 14 -- '-1' and '1': <Code Omitted>You will n

That is what those classes were designed to do (particularly the SmoothMover class).

Please show your revised bullet code.

Did you import the Smooth Mover class and have the SpeedBoat extend it?

Maybe its your browser security :?