Algodoo

Where's Homer?



Well, even without Homer, this scene is really cool. How do you come up with these ideas? I mean, you're just an ME, and this scene doesn't have any gears in it.

Thanks. I was thinking of making a _onDesignClick function that is an onClick function that works when the simulation is not running. This is just one step along the way.

I played around with your scene a bit and came up with a couple of ideas that you might consider adding to it as follows:

1. Provide a selection of "trigger" entities such as, 1. The mouse cursor (default), 2. One or more "scene.my.whatever_pos". With more triggers, a user has options to use either the mouse cursor, or to use some geometry pos. One caveat, and that is when there are more than a few items in the scene with your added code in them, the computer (mine) starts to lag very quickly with increased numbers.

2. Provide a choice of colors for the "hover" and the "non-hover" pos trigger.

3. Maybe provide a place to add personal code for the person who would rather have something else happen when triggered rather than a simple color change.

I'm sure I could think up more things for you to do, but that's enough for now! LOL

The new code addresses #3. So 1 out of 3 isn't so bad.

Nope, not bad at all!

I discovered an interesting effect after injecting the color changing code into the star. Using the knife tool, I cut the star into 7 or 8 ribbons, and then I ran my cursor over the ribbons. Cool effect, but you can't cut a polygon into too many pieces because of the lag issue which increases with the number of geoms that contain your code.

Nice job.

I tried the effect. It doesn't take many pieces to slow things down. If I convert the pieces to circles or squares then the response is much faster. I might be able to improve the efficiency of the pointInPoly function. I could consider the point is in a polygon if it's within the average distance between the polygon center and the surface points.