Love this approach. I used something like this in a course on the AN/TPQ-48 Lightweight Counter Mortar Radar. One of the initial modules required the student to unpack and inspect each piece in a certain sequence, so we simulated this with some informative drag and drop.
My concern with multiple slides instead of a multistate object is for mobile deployment. Of course the setup with multiple slides is fitting with the title of this post. You could even have using InBuilt states for the drag objects to show which have been dragged….
Sure, Greg, I have used this approach multiple times in projects. It is one of the examples I offer my trainees to have some more engaging interactivity since people seem to like dragging and works fine on mobile devices as well.
Not sure, but it looks like you navigate to new slides in the object actions? I tend more and more to use multistate objects instead of navigation to multiple slides, especially when the course needs to be reponsive to make it ‘sleeker’….
Did you use a shared action as object action or an advanced action, maybe even JS (do know you already a little bit).
This particular setup has five slides. Main slide and a landing page for each of the sports. The actions are based on which object is placed in the box. No JavaScript on this one – just a simple Jump to Slide on the object action as you noted.
I suppose I could have made that navigation persistent and changed the state of the background but I had in mind that the sport that was chosen might have much more content than could fit on a single slide so this idea takes you to a landing page for the chosen content.
So many options!