I used a button stack block and then a continue button. I locked the continue button to only allow the module to proceed after the learner clicks on all the buttons. However, when I preview my course, the continue button is unlocked before the button stack is ever used. Has anyone else run into this issue?
My colleagues and I have been frustrated by this Rise "non-feature" for years and have implemented the various options suggested by the user community. I'm not sure why Articulate doesn't monitor posts around this issue and push it up the "development pipeline."
In the interim, to make the Continue divider function with a Button block, will likely continue to build them in Storyline and insert.
3 Replies
Hi Kenneth,
In my experience, a Continue divider does not track Button blocks at all.
You are correct. I put an acknowledge section right after the buttons and before the continue button and it worked perfectly.
My colleagues and I have been frustrated by this Rise "non-feature" for years and have implemented the various options suggested by the user community. I'm not sure why Articulate doesn't monitor posts around this issue and push it up the "development pipeline."
In the interim, to make the Continue divider function with a Button block, will likely continue to build them in Storyline and insert.