sword move

All method calls are executed straight through. That is to say that only the end result of the method will be apparent to the user. The above is equivalent to this: and what is seen by the user is a single change in both position and rotation at the same time (if executed once). I presume this method is called by the act method of the class; in which case, the actor will be seen by the user to frantically revolve at about 12 to 15 complete circuits per second (and it would not look very esthetic) as long as the key is pressed. To animate something, you need to track the act cycles and perform specific actions along the way (moving and turning part of the way each act cycle). In other words, what you should be programming are the actions that need to occur during each act cycle. Some states that may need to be tracked are (1) is the sword being used (has the trigger been detected and has the actions of the sword not yet been completed); (2) where, currently, is the sword in its animation (is it on its down-swing, up-swing, changing directions or done moving).

If i use the move(-20) the sword rotates on the false side. And to be honest, i´m not sure that i understand what you mean. I tried to seperate the rotation with this: The problem with this was, that when it got smooth it also got to lame...i mean its an sword hit an as this it sould be fast. Obviously its very long, too. mfg, crae

is not the same as To give you an idea how to start:

You are so right. I did not think it through (that the turn changes the direction of movement). At any rate, the full change in location and rotation would still occur instantaneously unless broken down into smaller steps.

This code doesn´t work, sorry. If i click "v" it makes an attack, but only one time and the sword doesn´t go back (i suppose it should, because animation is false then). Second thing is: How can i use double numbers? With this i could put more part steps in one second. I tried this: mfg, crae

To use doubles, you have to write 'double' instead of 'int' in lines 3 and 4. Show the code which you tried when using my version. I still don't understand how you are trying to use this 'counter2' field. You aren't increasing it somewhere (or at least it isn't shown), you only set it to 0 when v is pressed.

Oh sorry, its not shown there. I use "counter2++;" in the act method. The integers were a mistake, i already wrote this with double - with the result that it doesn´t work. Well here´s the whole class: Ignore the sword images, i try to make it with "turn", and therefore i need the doubles...to put about, well i dont know maybe 15 turn commands in one second, so that it looks smooth, when "v" is pressed. mfg, crae

I think you misunderstand what 'counter2++' does. It is the same as 'counter2 = counter2 + 1'. In other words, it starts with 0 and will be 1 after the first act cycle, then 2 and so on. It will never be a number between 0 and 1.

I need it^^ With 1, 2, 3, ...i can only put a few turns in a second. So i can make it fast, but it looks crappy or i can make it lame and good-looking (smooth). The thing is i want both: a good looking movement, within 5-6 seconds. I mean if i make it with 1, 2, 3....8 i can put maybe 20 degrees in one act cycle, but this is too much. So if i go for well 1 to 16 i can reduce the degrees per act cycle to 10, but it takes twice the time.

Okay, again. If you have a counter which gets increased by 1 every act cycle, you can use 1, 2, 3, ... . It is the same if you do that or if you increase it by 0.1 every act cycle and use 0.1, 0.2, 0.3, ... . If the speed slider is in the middle (50), there are about 55 act cycles per second. So what would doubles change there? A counter doesn't need doubles, maybe the rotation/position needs it for smooth moving. What exactly should the sword do? A normal "swing" maybe takes 1 or less seconds. 5-6 seconds seem to be a long time.

Yep the rotation needs it. It should swing about 160 degrees. With every increase of the counter the sword should turn a part of this 160 degrees. If i take for example 8 act cycles, the sword have to turn 20 degrees per cycle (160/8=20). I tested this and the result is that this is too fast, it doesnt look smooth. So i tested 16 act cycles, which results in 10 degrees per cycle. This is ok, it looks good, but it slows down the attack, because there are more part steps. And now i try to find a solution. I thougt if i use doubles instead of integers for the counter and as a result for the amount of time, which is needed for the animation, i can make 16 turns in the same time as 8 with integers. For example: - integer 16 turns: 1=10°, 2=20°, 3=30°, ... , 16=160° (~55 act cycles-->16/55 seconds) - doubles 16 turns: 0.5=10°, 1=20°, 1.5=30°, ... , 8=160° (~55 act cycles-->8/55 seconds with the same amount of turns, but in the half of the time-->fast and! smooth attack) I hope i explained it understandable now :D mfg, crae

Ah ok, so you don't really want the movement in 5-6 seconds. 16/55 seconds is too slow? Well, there is no good way to make something show up in between act cycles and there aren't "half" act cycles. You can use the 'repaint' method and do like two act cycles in one, but your eye can't notice 110 images a second anyway. What you can do is, change the speed to 60 maybe. (Add 'Greenfoot.setSpeed(60);' in the constructor of the world subclass.) Then the whole scenario goes faster though.