Carousel Interaction Glitch

Mar 30, 2011

Brock Culpepper
By Brock Culpepper

I don't know if this is mentioned anywhere else on the forum or not, but I thought I would make this post just so Engage users can be aware of a small glitch I encountered in the carousel interaction.  After I built the interaction, I found the need to reorder my tabs.  Engage gives you the option to move to the left or move to the right to change the order of your content.  I almost missed it, but as I would move to the left or right, the tab I was moving would actually overwrite the content next to it, essentially now giving me 2 identical tabs, then 3, then 4 if I continued to move it.  This happened going both directions.  I just didn't want someone else to do this, not catch it, publish their course and then later find out their content is all wrong.  Hope this helps somebody!

3 Replies
David Burton
13 years ago03/30/11 at 1:43 pm (UTC)

Could you provide the exact steps to reproduce this issue. I was unable to reproduce this using the following method.

1. Create a new Carousel Interaction

2. Added an image to Step 1 (not the Inro)

3. Added an Image to Step 2

4. Published and viewed - no issue

5. Swapped Step 1 with Step 2 using the Move Step Button

6. Published and viewed. - no issue

7. Swapped Step 2 with Step 1 by dragging the tab order.

8. Published and viewed. - no issue

9. Save and Close

10. Open and repeat all - still no issue.

11. Repeat with 10 images - still no issue.

Please note, the Carousel Interaction and other Community Interactions do not have the ability to introduce any code or modify the core functions of Engage editor. If tabs are overwriting each other and can be seen in the editor, there is most likely an issue with Engage. Try reinstalling Engage, but more importantly make sure you are not working from a network drive as this can introduce the odd behavior you described.

Brock Culpepper
13 years ago03/30/11 at 2:38 pm (UTC)

It doesn't happen every time, but I essentially went through the same steps that you went through.  When this occurred, I can't say for certain that I wasn't working off of an Engage file that I had saved on a thumb drive.  I know that is a no-no.  Maybe that caused the odd behavior as you suggested would happen if working on a network drive.  I almost published the module without catching it...just didn't want anybody else to do the same and accidentally produce a flawed piece of work.

This discussion is closed. You can start a new discussion or contact Articulate Support.