Basically, i need to drag the object all over the screen and in real time place the mouse pointer's position into a variable, and perform calculations as the object is moved.
This may be too coarse a grid for you, but have a look at the attached. I added some transparent objects and a drag object. As the object is dragged over the grid of transparent shapes, two variables are changed. Note: In this rough mockup, I only 'enabled' the upper right quadrant.
Unfortunately I am currently unable to open Aticulate. Corporate has installed Flashplayer 18. I am waiting to have Storyline updated.
One example:
I was tasked with teaching people how to frisk individuals for radioactive contamination.
The detector's wand is dragged over the "body" the simulated device begins to chirp, the closer it gets to an unseen contaminated spot, it begins to chirp faster. The closer it gets the faster it chirps.
This can only be accomplished if the wand can be moved in any direction and it's position relative to the contaminated spot continually updated. It also had to not respond if the wand was moving too fast.
Yes, the 'hotspots' are transparent objects (you could use actual hotspot elements too). The variables are updated with triggers like this one:
As I had mentioned, the grid in my example is rather coarse. You could add more hotspots to ensure the variables are updated more frequently. I just thought that this concept might work for you.
That does help. So it really isn't the mouse that needs to trigger the interaction, it is the object hovering over an area that triggers the variable.That makes more sense.
I'm not sure how you could make it so that it would not work if the learner moved too quickly.
17 Replies
Hi Allen,
Are you using Storyline 2? A slider would allow you to do that.
There are a lot of examples of how to use them in the forums - so you may want to search through those as well!
A slider allows movevent in a linear direction. I need movement in 360 deg.
Basically, i need to drag the object all over the screen and in real time place the mouse pointer's position into a variable, and perform calculations as the object is moved.
I'm interested in seeing if you can get this to work.
I've been doing this in Toolbook for over 13 yrs.
Don't know how to do it in Articulate.
I've produced a number of real time equipment simulations using this technique.
Hi Allen,
I'm trying to visualize what you mean. Take a look at this and see if it helps.
This may be too coarse a grid for you, but have a look at the attached. I added some transparent objects and a drag object. As the object is dragged over the grid of transparent shapes, two variables are changed. Note: In this rough mockup, I only 'enabled' the upper right quadrant.
Unfortunately I am currently unable to open Aticulate. Corporate has installed Flashplayer 18. I am waiting to have Storyline updated.
One example:
I was tasked with teaching people how to frisk individuals for radioactive contamination.
The detector's wand is dragged over the "body" the simulated device begins to chirp, the closer it gets to an unseen contaminated spot, it begins to chirp faster. The closer it gets the faster it chirps.
This can only be accomplished if the wand can be moved in any direction and it's position relative to the contaminated spot continually updated. It also had to not respond if the wand was moving too fast.
While you are waiting for SL to be installed, here is the published version of my rough example.
Michael, thanks for the demo. It appears to have a number of "hot" spots.
As the object hovers over a hot spot, a variable is updated.
Is this correct? An excellent work arround. WIth enough "hot" spots could be made to work in most applications.
Yes, the 'hotspots' are transparent objects (you could use actual hotspot elements too). The variables are updated with triggers like this one:
As I had mentioned, the grid in my example is rather coarse. You could add more hotspots to ensure the variables are updated more frequently. I just thought that this concept might work for you.
I understand the concept. Thanks again. As I said, an excellent work around.
It is an approach I had not considered, and may be able to make it work.
Cary Glenn, did my example help you to visualize the concept?
Hi Allen,
That does help. So it really isn't the mouse that needs to trigger the interaction, it is the object hovering over an area that triggers the variable.That makes more sense.
I'm not sure how you could make it so that it would not work if the learner moved too quickly.
Toolbook has a scripted programming language similar to C.
It is very powerful. I've used Lectora as well. It can't be done in Lectora either.
The inherent response time provided the "don't move the mouse too fast" function. Other wise I would had too build in a timer.
It is the mouse's position that is evaluated continually. The routine must always know the mouse's position relative to the target object.
This discussion is closed. You can start a new discussion or contact Articulate Support.