Desmos Demo - Content Sink (Providing Feedback) - Guess My Number Activity

Hey y’all! I just finished up the next video in my Desmos Demo series where I break down how to use the content sink in your note component to give students immediate feedback. I tried something new with this one and added some additional support slides at the end as a review and would love any feedback/suggestions!

Video link:

Activity link:

Slide deck:

1 Like

Maybe not for this video because it might complicate the objective of using the content sink, but…

If you use the capture sink in the input CL and lastValue in your feedback conditional, students would be required to click the “Submit” button (“Share with Class” in your example) before feedback is given
In input CL:


In note CL for feedback variable conditional:

instead of {g} use {input1.lastValue(“g”)}

I like this because it avoids changing the feedback as soon as the correct guess appears. For example, if your number was actually 2, but a student was guessing 2.5, the feedback would say correct even though the student did not actually intend to guess 2.

1 Like

This is a great idea! Someone in the Desmos Educators Facebook group brought up this issue and mentioned adding input1.submitted to the conditions in ordered to correct the issue . Do you feel like capture and lastValue could be a better solution?

Actually, yes that works better. I’ve just gotten used to using tables for answer entries, and capture works best for that.

So, I would just do a nested conditional:
when input1.submitted (
“your original conditionals”)
otherwise “”

So I’ve actually never thought of using a .submitted on the outside to cover my previous conditionals but that’s a great idea!

The current method is:
When n=g and input1.submitted ____

And that’s repeated for each possible outcome. I’m definitely going to make that change in my practice though!

Can you talk to me about the benefit of capture over using “when timeSincePress>0”? That’s been my method for using tables but I’m always looking for more efficient/effective methods

If you use timeSincePress>0 and the student has an opportunity to change an answer, the feedback will automatically change once the correct answer is typed without having to resubmit. capture is a stored value when the button is pressed, so a student must press it again to get new feedback.

I often limit the number of times a submit button can be pressed so students can’t just put in guesses, particularly if I’m using it as an assessment. timeSincePress would give them unlimited opportunities.

I also use capture in combination with isEditable to lock a cell once a correct answer is submitted. I’ve had students accidentally delete answers in tables by accident.