Lyberodoggy wrote:You should "click" it when the frame or event starts using the same command
Action.SimulateHotspotClick(1)
Yeah, I haven't added in automatic calls yet. I was just trying to keep it simple (KISS) until I figured out how to do it. Would not having the call in the frame cause an issue?
Lyberodoggy wrote:Also, what you did there was pretty good. It's called routine self-call and works like a loop. But you got something wrong. What you want to be timed is the calling, not moving the hotspot.
Oh! Is there some reason why this is better?
Lyberodoggy wrote:I also modified the code to work without any variables and for any given hotspot, to eliminate the variable problem that also exists in my plugin.
- Code: Select all
Hotspot(GetHotspotNumber).move Hotspot(GetHotspotNumber).width, Hotspot(GetHotspotNumber).height+150
Action.CreateTimedEvent .1, "Action.SimulateHotspotClick(GetHotspotNumber)", FALSE
How does (GetHotspotNumber) work? Do I have to pass the Hotspot number as a parameter somewhere? Or does it grab it automatically? If so, when? On mouse click or frame load, or what? If it's on mouse click, this means I'll have to call every hotspot on frame load, doesn't it?
Thanks a lot!
Oh - I also need to change this part:
- Code: Select all
Hotspot(GetHotspotNumber).move Hotspot(GetHotspotNumber).width, Hotspot(GetHotspotNumber).height+150
While the y is a steady fall, the x needs to be at whatever location the hotspot starts at. Remember, I'm trying to make a random number of falling objects that fall at different intervals, and with different speeds (eventually). Right now, I'm working on the simplest case - just get it moving, make it stop.
A woman on a mission - a budding artist looking for a place to take root, a builder looking for the right community - I'm looking for a home.