no more need to monitor the DOM and hide the '@3' elements
no more chance for users to accidentally select or delete the '@3' characters.
simplifies a few other things
Main difficulty with this would be changing the expression id in place without (a) moving the expression or (b) recalculating everything. setExpression would not work because that keeps id constant. Could probably just remove the expression then tap into Calc.controller pretty easily to dispatch a new expression event.
Alternatively, use some other property of expressions (like colorLatex or pointOpacity or something else that supports arbitrary strings) to store all metadata, including being a DesThree expression.
This is a very simple solution to many problems.
Main difficulty with this would be changing the expression id in place without (a) moving the expression or (b) recalculating everything.
setExpressionwould not work because that keeps id constant. Could probably just remove the expression then tap intoCalc.controllerpretty easily to dispatch a new expression event.Alternatively, use some other property of expressions (like
colorLatexorpointOpacityor something else that supports arbitrary strings) to store all metadata, including being a DesThree expression.