Removing or Hiding the Previous/Next Buttons?

Hi all

I am having an issue when publishing my file too. I have an assessment with no default buttons. When I click the Retry button, the Next and Prev default buttons from SL appear apparently randomly. All my slides are set to "reset to initial stage".

I don't want to see the SL buttons at all, never. It is not a review of the quiz. I just want the learners to be able to retake the assessment as many times as they want, with the questions looking exactly the same.

I've had this issue with at least 2 other completely different projects, with one isolated question for example. Do others have that too? I am publishing on my C: drive.

Hi Helene!

Would you be able to share your .story file for us to take a look? You can share it here via the 'Add Attachment' button in the bottom left of the reply window or here privately.

Hi Leslie. Done.

Thanks Helene! I will respond to you via your case.

I have inherited a module that includes a quiz that employs a temp variable counter: the user drags a total of 10 rectangles into one of two columns (green or purple). When all ten rectangles have been dropped into the two columns the count reaches ten and the next button appears.

However, if you drop one rectangle in either column (right or wrong) multiple times, the count also reaches ten and the next button shows - not desired behaviour. If the user gets 7 right and 3 wrong, again 10 is reached and the next button shows - not desired behaviour.

Sometimes the next button will not show in flash after the user has started, then presumably gone away for a while and restarted the quiz. So the user get's lost.

What logic can I add to prevent the counter reaching 10, until all ten have been dropped into the correct column/s?

Hi Rob!

Would you be able to share your .story file or even sample slide in .story format? This may help in allowing someone to better assist you and understand the setup.

Hi Rob,

It sounds like you're also looking to ensure that the user has dropped the item correctly vs. just dropped and left it in a column. Without seeing your triggers (which you can share the file as Leslie suggested) my guess is that you're adjusting the variable based on the item being "dropped" - what about adjusting the variable based on the item having the state change to dropped correct? You could set that state to look exactly as the normal state so that the user wouldn't know if they were correct before being able to advance with the next button. You'll also want to ensure that you don't select to "delay item dropped state" until submitted within the drag and drop options. 

Ok, after much ado I figured it out. You set all (in my case) ten rectangles states to 'drop correct' when they are dropped into their respective 'correct' columns. Then you change the 'next' button state to 'normal' (state set to hidden at start of timeline) when 'state' on 'All of' ten rectangles are 'Drop correct' I had to double check 'all' rectangles had their state set to 'drop correct' when dropped on the correct column. I had accidentally left one as 'normal' which prevented all ten being counted as complete. Happy with the results now. Thanks for your help here, you set me on the right course; the rest I figured out for myself - the best way to learn!

A real fiddle-faff, but now I feel a lot more confident about using Articulate :-)

Thanks Rob for the update and so happy to hear you were able to determine a method that would work for you.

I have removed all buttons from the bottom of my player. Problem is that Storyline is scaling my stage to fit that bottom space. In the attached image, you can clearly see my Story dimension of 988 X 643 are being scaled (Stretched) both horizontally and vertically when I remove all bottom buttons. How do I prevent the scaling?