Algodoo

Nice idea, and a very useful tool.

Thanks.

I don't know how, but when I play some scenes, and even go do different scene, or to blank one, sometimes I still have code forcing "mode=sim.running" and only way how to get rid of that is reset to default settings (I know some people are using it to secure their sims)
Is there a way how to get rid of it? Where in console is this code running?
Can I report a scene for doing this, without me knowing it? Because it makes me mad when algodoo is doing things on it's own, outside the scene I downloaded
A.k.a it is harmful program for me that I don't know to turn off = virus

Regarding "App.GUI.playMode = sim.running", as far as I know that will only work in an object and can't be done at the root level. If you still have code forcing "mode=sim.running" when you create a new scene, then check the last few scenes you downloaded to see which one caused the problem. If you locate the scene, then you could post the scene's url in the comments here and I can look for the source of the error. Some scenes put the "App.GUI.playMode = sim.running" code in the update event of an object, so there is no way of getting out of playmode for that scene. Loading a new blank scene should not automatically start playmode (assuming you shut it off before starting a new blank scene.

Q: Is there a way how to get rid of it?
A: Yes, use the phunlet in this scene.

Q: Where in console is this code running?
A: I don't have a clue. The console does not retain any code. As far as I know, the only code that runs in the console is temporary code that a user puts there. Code that caused problems for me has always been in a scene. Usually its the result of Algodoo tripping over some code and causing unintended damage or a user creating variables at the root level instead of using "scene.my." variables.

Q: Can I report a scene for doing this, without me knowing it?
A: Maybe, but it usually helps if you identify the scene. Otherwise it's reporting that one of the 158,000+ scenes is causing a problem but you don't know which one it is.

"it makes me mad when Algodoo is doing things on it's own, outside the scene I downloaded"

Some settings persist after the scene is closed, some don't. If a scene creator is going to change a persistent setting, then the scene can read the the users settings when the scene is opened and put them back when the scene is closed. Even this will fail if the user loads a new scene without closing the old scene. Most user's (including me) don't know which variables are persistent and which aren't.

My suggestion would be to find the culprit and tell him in his scene comments that you don't like what he's doing. Most scene creators don't cause problems on purpose.

P.S. An example of a scene breaking the config file can be found at Bacteria under the microscope. Load the scene. Open the console. Start the scene. A few warnings come up. The damage is done. Enter sin(0.75) in the console. Algodoo says it doesn't recognize the function. Close the scene. Reset the config file. Open a blank scene. Open the console. Enter sin(0.75) in the console. Algodoo shows the correct answer. This is an interesting example. I'm sure matto did not do this on purpose.