tamasocal.blogg.se

That way, if they require greater precision, they still know that they will need to find a different tool.

It is important that we let the user know that we did that, though. We can handle those cases automatically, effectively short-circuiting that manual step. The user is left with a couple options: manually trim and try again or try a different tool. I partially agree with that modifying the input and losing precision without letting the user know is not a good move, but I also think we can improve the experience. We can improve the experience for pasted input, though. For keyboard input like this, we should continue to rely on the button that allows users to enter in numbers in scientific notation: I feel like that might be confusing to users and a little awkward to display. I do not think we should allow users to type in numbers beyond the maximum number of digits and automatically convert to scientific notation. This is my first time working on this project, so I'm pretty ignorant atm, but I'm hoping I'm at least in the ball park : )į I change that TryAddDigit call it will mean the user could type in digits over the maximum number of digits (as well as copy paste them) and they would automatically be converted to scientific notation. There may also be a better way to tackle this that I'm not aware of. And that's not something I want to be changing without input.

The reason this needs a design decision, is that if I change that TryAddDigit call it will mean the user could type in digits over the maximum number of digits (as well as copy paste them) and they would automatically be converted to scientific notation. This was because of the TryAddDigit call here. Instead all of the digits after the maximum number of digits were getting cut. I figured out that the error throwing based on length can be removed by removing this operand length check.īut while the calculator was not longer showing the "Invalid Input" message, it was not getting put into scientific notation.

Hello! I tried to give this a shot, but I ran into a problem that I think requires a design decision which I'm not able to make.