[phkahler]

That linked description is very interesting. They list 3 steps that need to happen to get an incorrect dose. The 3rd step is that YOU confirm the dose. The next section emphasizes the importance of confirming it. That's all great, and yeah, the user basically hit OK but that does not change the fact that they have a software bug.

Also, since it happens intermittently with that kind of input I have to seriously question how the software is put together. If the input box shows the decimal there's no way it should slip past the parser. Something smells very wrong with how their app is put together, and that would make me concerned about other issues we just don't know about yet.

[jacquesm]

> that would make me concerned about other issues we just don't know about yet

That's exactly my concern. This is not the kind of bug that you fix and move on, this is the kind of bug that makes you go back, fix your process, ensure your QA would catch this next time and then you audit all of your code to make sure that your broken process hasn't missed anything else.

[omh]

Also it would be very possible to misread the confirmation.

If I've just entered "0.21" then when the confirmation screen reads "21" it's not immediately obvious that it's wrong.

[WirelessGigabit]

It doesn't happen when you put in ".21". It happens when you put in ".21". Little less obvious.

[jacquesm]

> It doesn't happen when you put in ".21". It happens when you put in ".21". Little less obvious.

It's so much less obvious that I'm going to ask you to explain the difference to me because for the life of me I can't see it?

[WirelessGigabit]

Okay I even made the mistake here.

It happens when you put in ".21", not when you put in "0.21". If you omit the leading "0" it might drop the leading "." too.

[jacquesm]

That makes more sense, thank you for the update.