Algodoo

Very clever! Nice job!

Just a couple of suggestions:

1. Disable the Algodoo clouds. They are not necessary for this scene, and they can be very distracting.
2. The arrows fade out after 5 seconds. Either make the fade time selectable by the user, or make it infinite.
3. The arrows get created when using ANY of the Algodoo tools, but that can be a problem because you do not want arrows being generated when trying to add gears, polygons, or other geometries to a scene. Maybe make the arrows work only when the Drag or Move tools are being used.

Thanks!

By the way, "wild bill" is now the official Algobox Admin. I still help him occasionally, but most of the duties are on his shoulders now.

Xray
1. Yeah stupid clouds!
2. That's the point
3. Because it is just one function for this scene, normally it will be used for moving and facing units (as WarCraft movement)
Also don't know how to "read" which tool's is active
I know there was some way to block algodoo tools or just temporary unbind them

For me, YOU are the only admin! (Hope Wild bill won't see this comment)
Sorry for inactivity, I'm on university and now I have same time between exams
Guess who get "A" from programming?
P.s.: They know about algodoo here YAY Funny thing is that they only know how to play it, not how to program it

Jakub -

You said: "2. That's the point". Oh, so the delayed fadeout is supposed to be that way? I obviously did not understand how these arrows are supposed to be used. It makes sense if they are supposed to be temporary, but I still don't understand what they are intended to be used for. Sorry, I am not familiar with the game WarCraft.

You said: "Also don't know how to "read" which tool's is active". I don't know how to read which tool is active either but I know how to select them. For example, if you want to force select the Drag Tool, the command is: Tools.DragTool.SelectTool .....And it's the same command for all other tools, just change "DragTool" to whatever tool you want to be selected. For example: Tools.BoxTool.SelectTool. I'll let you know if I figure out how to determine which tool is selected.

You said: "For me, YOU are the only admin!" ...Awwwww, how sweet!

You said: "Guess who get "A" from programming?" .... Ummmm, kilinich????
LOL LOL..... Just kidding. CONGRATULATIONS!

You said: "Funny thing is that they only know how to play it, not how to program it" .... That's because they never seriously explored it! Algodoo is just a simplified version of some other script type programming languages. It has similar commands, and similar handling of memory functions. For example: scene.my.variable2 = 3.14159. It can also handle reading indexed arrays, but it does not easily write to indexed arrays. For example: It can read array data like this: _CatVariable = scene.my.DogArray(27), but it CANNOT write (store) that same array data like this: scene.my.DogArray(27) = _CatVariable. That has been a complaint of mine for many years, although there is a workaround to make that work.

You produce some really good scenes, and so I hope you can spend more time in between your schoolwork making and posting more really good scenes.

Jakub --

I noticed an error in your code. Each time I create an arrow, Algodoo prints error messages in the console because of two invalid commands in postStep. One is _down(true) and the other is _up(true). You need to remove (true) in both cases. So, if you edited them correctly, one will be _down, and the other will be _up. You can execute the code in a local script simply by writing its name!


That's all!

Great idea. Well done. I'm sure you win the Algodoo prize for most efficient use of textures (although your piston.png is slightly smaller than spika.png). I may try my own version of this scene. If I do, then keep in mind that "Imitation is the sincerest form of flattery".

Thanks for comments, I left most of my programms and self-writen "book" of algodoo programs and I'm also learning new program so I make more mistakes in scripts now
Programs we use: MatLab, Inventor, autoCad -will use: solidworks, creo
- How to make direct acces to array?
- Will fix that (true) problem, I'm not sure when that (true) is needed then, but this thing I learned from YOUR scene
WarCraft is really old game, even my dad know about it, it is just command for units, first point is where they will GO, second point is where they are FACING so they will SHOOT where arrow is pointing
Update from school: math exam is DONE! YAY

How to make direct acces to array.
(true) is needed when the function expects a Boolean input parameter.