Hi
I want to add a button(submit) to the table. I’m unsure how to link the button to the table. I have scanned this site and searched extensively on YouTube. Came across excellent videos by Ryan De Le Garza.. but somehow what I envision is lost in translation with me. Somebody who can explain this to me as if I were a 5th grader would be greatly appreciated.
Thanks
You can place an Action Button below a Table or above it, but not part of it. You can only combine the Action Button where it appears on it with Graph or Geometry components. See this activity.
Thanks for posting!
Can you give some more information as to what you’re hoping to achieve with the button?
I think it could be a custom check button, instead of Desmos automatically checking the input
@NTMDev That’s what I was thinking as well.
@Poovandrie_Jansen Here is a mock up of a screen similar to the one that you have above. A couple things I want to point out:
timeSincePress function called in the table. By defining the time using this and telling the cellSuffix not to appear until that number is greater than 0, the feedback doesn’t appear until the button is pressed. Time resets when the table is interacted with or the “Edit” button is pressed (still the same button, just in reset mode).resetLabel that makes the button show “Edit” after it is pressed. This also stops the timeSincePress timer.Let me know if you have any questions!
Nice someone else also agrees! 
I wonder how you would make the checking manual? Maybe like make an action button update a variable, say checkAnswerBoolean (default false) to TRUE, then we have a check: checkAnswerBoolean? Not sure if this would work.
Also (not sure if I’m on the same page as you) for:
Can’t you just do hidden: this.pressCount = 0 to see if the button was pressed to then show the feedback?
It really depends on if the you want the feedback to reset each time, or for it to persist. By using timeSincePress, the feedback will reset as things are edited as the time resets. However, pressCount won’t ever reset without some other trickery.
I find it a little cleaner on the eyes for the feedback to disappear whenever the table is edited so that isn’t updating in real time as the student makes changes.
Oh really? So from what you’re saying, if I edit something like a element in a table from 1 to 2, the timeSincePress will default back to 0 again?
I believe that just putting a cell in focus in the table should do it, but yes! It’ll reset back to 0, but pressCount will not. You can test it by setting a variable in the CL and then pulling it into a note to see it reset in real time.
This table focus resetting buttons is a very long standing bug that has never been addressed. Very unfortuante it’s still there.
Oh it’s a bug? It makes sense to me.
Honestly this could be a cool feature for giving feedback.
I’ve never been told it was a bug, but there are some things that are bugs turned features. It has always made sense to me as well.
Every time a table cell receives focus it should reset other components?
It breaks every button instantiated animation you’d care to run and isn’t at all semantic. User focus changes should not affect state change in other components.
It’s not in keeping with normal web based animation behaviors and a quick search here will reveal how much of a headache this has been over the years. It’s another thing that should be opt-in, but unfortunately it’s not even opt-out.
I think the intention would be so that if a student were to change a value in table that has an effect on the animation, then the animation would start over.
A lot of times we work around this by disabling edits to the table until the animation is completed, if needed/desired.
And if entering values in a table is not related to the animation running? Or if the animation itself is important to working with the table? You see the problem.
Notably, the Desmos Engineering Team agreed this is a bug and fixed it as far back as 2022(which I can verify through some pull requests I made for it with them), but it seems to have crept back into the codebase unfortunately.
Just search for “reset table focus” on this forum to see how much aggravation this has caused people over the years. It’s not good UX.
@Mike_Gleeson Out of curiosity, do you recall if it was fixed for the native table submit button, or any action button, or both? I guess I’m just wondering if it was only the table submit button that was fixed, which has since been deprecated, and we’re left with action buttons.
Wait, there’s a separate submit button for the table? I haven’t seen it before… is it default to hidden?
The fix was supposed to - and actually did for a short while - apply to all action buttons on the entire page. Table focus should not reset any of them. Just looking at the email now about it, and that was the fix implemented.
I even posted happily about it(last comment in that thread) when that bugfix was pushed through, but sadly I may have to retract that happy post as it reverted back at some point not too very long after that if memory serves.
Isn’t Daniel a CL/Amplify employee? Can’t he just directly change this? I’m curious too if this will get fixed.
Daniel and I are both CL Specialists with Amplify. While we can’t fix it directly as that takes work from the engineering team, we can attempt to push it up the chain about it being fixed again.