Digital Workshop

When I'm, bored--I play with my snake!!!

This was done in OpusScript. It eats processor power if you move it too fast.

I have a clock version as well, but I got bored before I finished it, so it doesn't re-assemble itself when the cursor stops.

Cheers Sandyn,

Works brilliantly - very smooth snaking. BTW - It would make a great screen saver.

Mack

well done!

Thanks!!
The original idea came from the java clock which can be dragged around the screen (if you have seen it?) The numbers and hands follow the cursor, but in a delayed fashion, so the clock appears to break up as the cursor moves, then re-assembles itself when the cursor stops. I wanted to see if I could reproduce that in OpusScript.
The snake was the first stage to get objects to follow the cursor.
It's only a few lines of script, it uses an event handler and arrays. When the mouse moves, it's position is saved to the first element of the arrays, then the previous 12 positions are rippled back through the arrays, but an increasing delay is added to the setposition.
I then used the DW analogue clock demo and the script to create a draggable clock. This works fine. When the cursor moves, the face, numbers and hands follow the cursor, when it stops, the clock re-assembles......however when it is published, it grinds to a halt. I used some lazy programming, so I need to go back and try to optimise the program.
I also started to develop a game based on the snake, but Opus is not really suitable for this. With an average spec. PC, it soon runs out of power when you use event handlers which have a lot of calculations in the scripting . It's an interesting challenge.

The screen saver idea is very interesting!. Rather than using the mouse cursor position, random movement of the snake.

Sandy

Sandyn

Thinking out loud...
would it make sense to create a Frame, or a Rollover or Hotspot object for that matter... that on MouseOver activates your script. Makes for sort of "an active zone". Then move that zone along as well.

I would assume you could also put a Wait state or ticker/loop to reduce the sampling and monitoring?

You're right... even on a somewhat modern machine, it's easy to outrace the CPU. Nice work on the effects with slower mouse excursions.

Thanks for some good ideas. One method I had thought of was to use the event handler to increment a counter, then when the counter reaches 10, run the script. Effectively dividing the event handler by 10. It's a trade off between smooth response and CPU usage.

I don't understand why it runs slower when published??

Sandy