Algodoo

1. There are no instructions of how to start/stop the motor and how to change speed.

2. It's not good programming practice to write data to a variable from two different locations. For example, you show "text = scene.my.attract3" in "PostStep" and in "update" within a geometry. That could cause conflicting data. Hint: "PostStep" executes code only when the scene is in RUN mode. "update" executes code when scene is in RUN or PAUSE. Do not put code in "update" unless you have a very good reason for doing so!

Other than those suggestions, you did a great job on the scene!

Thanks Xray. I will delete the code i forgot to delete in "update",
i think you mean those boxes i only left there for debugging purposes for experienced users.
Its also good to know where the difference is between "update" and "postStep".
And yes, i forgot to put some controlls into the description,
i was just afraid of getting banned for uploading stuff too many times.

for some reason the text doesnt changes, if i put
"(e)=>{text = scene.my.attract2}"
as example into "postStep"?

You: "I was just afraid of getting banned for uploading stuff too many times."

Me: You will not get banned for EDITING a scene many times! You may edit a scene a hundred times if needed. What will get a person banned for a few days is if they post more than 3 individual scenes in one day.

Also, I'll take a look at your script to see what the problem is, and I'll respond here after I figure it out.

UPDATE: Okay, here's the problem. In your code:
text = scene.my.attract1, the value located in the variable scene.my.attract1 is not in the correct format. In order to display text, the value must be in TEXT format, and not just a numeric value. You can do that by adding quotes to the code, which forces the text display to correctly display the data that's in the variable. So, you need to change the code to: text = "" + scene.my.attract1. When the text function sees the double quotes, it then assumes that the value in the associated variable is text and not simply a numeric value. Do the same with scene.my.attract2 and 3.

One more thing. By enabling both lasers, you run into the same problem that I mentioned earlier. That is, you are forcing the code to write different values to the same variables at the same time which is not recommended. By doing that, the scene might run erratically or may possibly freeze up. Besides, it doesn't make sense to try to run a rotating device in two different directions at the same time. Instead of telling users to delete a laser to change direction, why not just tell them to press the i instead of the u, or vice versa!

Hope this helps.

Update: meanwhile i was searching in algodoo wiki for how to make a "If ... Then ... Else ..." and did some coding. anyway thx, im gonna read every single Letter in your reply.

oh yes, for the problem with the code that gets forced to change the value of one variable is something i couldnt fix due to the design issue that this motor has, unless i take it the ability to spin in two different directions, wich wouldnt be a benefit at all.

Oh well.... We are not programming ICBM's with nuclear warheads, and so a little messy code is no big deal!

yea, i agree with that!