I'm fairly sure the refresh is an inherent part of JSInput problems. I use the SetState function to make sure everything is back the way it was before, so students just see the flicker and not a total reset.
I'm glad it was helpful to you! Last I talked with Stanford they were happy to have more JSInput problems added to that repository, so if you are able to share your code, please do. On Mon, Jun 20, 2016 at 11:03 PM, Daniel McQuillen < [email protected]> wrote: > Hi Colin, > > A question about the "check" process within the larger problem XBlock when > using this example or others from the Stanford/js-input-samples repo: > > I noticed in the example projects that the iframe gets refreshed when the > user clicks the problem's "Check" button. Do you know if there's a way to > prevent that refresh cycle, or is it a required part of the check process > when using JS input? > > BTW, after watching your informative talk on XBlock > <https://www.youtube.com/watch?v=-cDm5i2li6I>s from a couple months back > and taking the sample code for a spin, I was able to get started really > quickly. Thanks for sharing your knowledge! > > Thanks, > > Daniel > > -- > You received this message because you are subscribed to a topic in the > Google Groups "General Open edX discussion" group. > To view this discussion on the web visit > https://groups.google.com/d/msgid/edx-code/34d4dfa4-aa09-4031-9cd3-2f002da2b1ff%40googlegroups.com > <https://groups.google.com/d/msgid/edx-code/34d4dfa4-aa09-4031-9cd3-2f002da2b1ff%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "General Open edX discussion" group. To view this discussion on the web visit https://groups.google.com/d/msgid/edx-code/CABmE_WKmMVG9zUyV8ULLWiJERS9TeixAG0dys4TYhp%3DUX%3D8NJw%40mail.gmail.com.
