There’s a script button on the screen (it’s at the upper left) that’s not associated with any of the parts (the note, the responses, etc.). If you click it you get an empty script editor. What’s that for? It seems like it would be a good place to put shared variables, but I can’t seem to access it.…

They are undocumented, but some sinks that can be used are title:, subtitle:, and coverText:.

Interesting. And subtitle and coverText aren’t available using the UI, it seems? Are there other uses for that screen-level code block?

Graham_Charles , like you I’m curious about the screen script button. As a general approach, I was hoping to placing a Boolean there for the next screen to check that any necessary conditions for progression have been met and, if not, sending the use back to complete whatever is missing. It seems odd…

Your coverText is generally conditionally dependent on another component, so set your Boolean there and refer to that.

Sorry Daniel, I don’t understand your answer which probably means I didn’t explain what I was trying to do adequately! Here is a 2-slide example with comments. I don’t want the student to advance until whatever is on screen 1 has been completed.Ideally, I’d like to disable the ‘next’ button but fai…

Here’s an example of what @Daniel_Grubbs was referring to: [image] Asynchronous pacing Discussion That’s the button that you would use for the coverText and setting the title on the screen. Try typing in a fake sink and the error message will tell you all the possible sink…

Thanks @cwinske , I now understand what @Daniel_Grubbs was saying, and see that that is a very effective way of hiding what is on the second screen. I think the approach could be made even more general if there was some way to refer to the screen script on the preceding screen, using code of the form…

Are you trying to say everything intended on the previous screen needs to be attempted before moving forward? Maybe a feature request. For now, your only option is to give those specifics, although you could define them in one component in the previous slide to get similar functionality.

[image] Daniel_Grubbs: Are you trying to say everything intended on the previous screen needs to be attempted before moving forward? No. I’m trying to say that the condition for moving forward be consolidated into a screen script to avoid the following screen needing to know about the specifi…

So, you’d still need to define those conditions in the previous slide, which you can do in another component as an alternative.

Screen script button

Questions

cwinske January 19, 2021, 6:11pm 7

Here’s an example of what @Daniel_Grubbs was referring to:

Topic		Replies	Views
Asynchronous pacing Discussion	9	3048	September 25, 2020
Cover Screen until previous screen is complete? Questions	2	1075	January 30, 2022
Screen Lock with CoverText Questions	1	1029	March 6, 2021
Correct answer before moving to next slide Questions	14	4321	November 15, 2024
I Made a Button Game (Alternative to Disabling "Next") Discussion	5	1996	August 9, 2020

Screen script button

Related topics