I've noticed a bug that prevents all Jump to Slide functions from working until all draggable objects on a freeform drag and drop slide have been displayed. I'm wondering if there are any work arounds or do I need to submit a bug fix request? It means that Forward and Back buttons and Menu buttons are disabled until the last draggable object is displayed.
Oh, no. The interaction itself is fine but what I haven't noticed before is that the normal navigation buttons are disabled so if the user wants to leave the interaction by clicking forward or back they can't. They have to wait to all objects have been displayed. Normally, you don't see the problem because all objects are normally displayed at the beginning of the timeline but if they aren't or if you choose the "Reveal drag items one at a time" option then you can't jump out until the last drag item is eventually displayed.
Hi Gordon by design the Submit button is checked in the slide properties and the Next /Prev buttons are deselected for a quiz type slide. But if you want to have the nav buttons display just check them.
I get the same behaviour if I set the D & D options to reveal one at a time - I can click next after the first of four items are revealed. Are you using this option or are you doing something else?
Perhaps it might be easier for someone to help if you can upload the slide and people can see your setup.
Unfortunately, the file size is too big to upload due to the amount of video. I will play around with some simple examples as you have done and try to determine the pattern. Thanks for your help.
Hey Gordon- this might be a shot in the dark, but is your question ungraded? And if so, is it set to required or optional? Also, is your menu set to Restricted navigation?
I noticed in my testing (ungraded, required, restricted navigation) that if you click on Next or try to use the menu to move to the next slide, nothing happens. But if you click Next a second time, it moves to the next slide without having to complete the interaction. That does seem buggy to me. I would expect not to be able to move until the interaction is completed if the setup matches the above conditions.
Also, if you hit the submit button (which will prompt you to complete the question), and then hit the Next button, it will allow you to advance. I'm going to submit a report to our QA team for this setup, and once we have some information from them, I'll be able to update this discussion.
If you have a different setup, let us know, and we can test that out as well. You are also welcome to share your file with our support team by submitting a case.
We've actually figured out the reason that the second click was working on the Next button... when the navigation is set to restricted, the timeline on the slide must complete before the Next button will work. So once the timeline is complete, the Next button becomes functional. Gordon, how long is the timeline on the slide? And if you wait until that timeline finishes, is your Next button functional?
This is all based on my grand assumption that your setup is with restricted navigation. ;)
I've done some more playing around and have now fully identified the exact nature of the bug. It actually has nothing to do with drag and drop interactions. It will effect any screen where a smart shape's fill is set to "Slide background fill". If such a shape does not display at the beginning of the timeline then all navigation buttons are disabled until the shape displays! A very quirky bug. The solution for me was to set a solid fill and all problems were solved. Please pass on this bug info to your development team.
This one has actually been reported to our QA Team. I will add this thread for their reference and so we can update when applicable. Thanks for the details.
15 Replies
Hi Gordon
what behaviour are you after that the user only has to drag a few of the objects?
Oh, no. The interaction itself is fine but what I haven't noticed before is that the normal navigation buttons are disabled so if the user wants to leave the interaction by clicking forward or back they can't. They have to wait to all objects have been displayed. Normally, you don't see the problem because all objects are normally displayed at the beginning of the timeline but if they aren't or if you choose the "Reveal drag items one at a time" option then you can't jump out until the last drag item is eventually displayed.
Hi Gordon by design the Submit button is checked in the slide properties and the Next /Prev buttons are deselected for a quiz type slide. But if you want to have the nav buttons display just check them.
Hi Wendy,
It's not that they're not displayed. They just don't work until the last draggable item is displayed.
Hi Gordon
I don't get the same behaviour - see attached video. Perhaps I am misunderstanding your issue.
Hi Wendy,
In your example, all drag items are displayed from the beginning so there's nothing to wait for.
Hi Gordon
I get the same behaviour if I set the D & D options to reveal one at a time - I can click next after the first of four items are revealed. Are you using this option or are you doing something else?
Perhaps it might be easier for someone to help if you can upload the slide and people can see your setup.
Hi Wendy,
Unfortunately, the file size is too big to upload due to the amount of video. I will play around with some simple examples as you have done and try to determine the pattern. Thanks for your help.
Hi Gordon
you can create a new project file and just import that slide in if you like.
Hey Gordon- this might be a shot in the dark, but is your question ungraded? And if so, is it set to required or optional? Also, is your menu set to Restricted navigation?
I noticed in my testing (ungraded, required, restricted navigation) that if you click on Next or try to use the menu to move to the next slide, nothing happens. But if you click Next a second time, it moves to the next slide without having to complete the interaction. That does seem buggy to me. I would expect not to be able to move until the interaction is completed if the setup matches the above conditions.
Also, if you hit the submit button (which will prompt you to complete the question), and then hit the Next button, it will allow you to advance. I'm going to submit a report to our QA team for this setup, and once we have some information from them, I'll be able to update this discussion.
If you have a different setup, let us know, and we can test that out as well. You are also welcome to share your file with our support team by submitting a case.
We've actually figured out the reason that the second click was working on the Next button... when the navigation is set to restricted, the timeline on the slide must complete before the Next button will work. So once the timeline is complete, the Next button becomes functional. Gordon, how long is the timeline on the slide? And if you wait until that timeline finishes, is your Next button functional?
This is all based on my grand assumption that your setup is with restricted navigation. ;)
Hi Crystal,
I've done some more playing around and have now fully identified the exact nature of the bug. It actually has nothing to do with drag and drop interactions. It will effect any screen where a smart shape's fill is set to "Slide background fill". If such a shape does not display at the beginning of the timeline then all navigation buttons are disabled until the shape displays! A very quirky bug. The solution for me was to set a solid fill and all problems were solved. Please pass on this bug info to your development team.
Ah, I see. Thanks for the additional troubleshooting, Gordon! We'll do some testing on that behavior.
Hi Gordon!
This one has actually been reported to our QA Team. I will add this thread for their reference and so we can update when applicable. Thanks for the details.
This discussion is closed. You can start a new discussion or contact Articulate Support.