Hi Micheal, I know that, thanks for the link.
Still, I thought the whole goal of making programming visual was to make it easier and more accessible. This is counterproductive to that goal. Most people that use GH have no idea about programming, why are you bringing up programming? The common user does not care about the why’s. Honestly I don’t care either.
My GH is set up to display the maximum amount of decimals. Yet, that panel says 2.44.
You deliver a shoe to a client, it fails, are you going to bring up chemistry and try to explain why the adhesive failed or why the rubber melted? He won’t care. He will say, this should be working, I paid for it to work. You would then probably say “Here, take another shoe”.
I have this rounding issue present when I am working, I always use smaller than 0.01, or document tolerance and almost never use Equality. But this is different.
What is the point of explicitly telling the software to do something that I am already assuming it is doing by what it is showing me? It is not like I assume out of thin air. That panels says 2.44!
Make GH do this automatically. Round values to document tolerance.
I mean it does not take a genius to see that most people that use GH will stumble upon this and fail to solve it. It just so obvious…
As a developer, how can you expect so much from your user?
That is not really advocating on part of the user. We are not protecting the user here. In the words of Bob Tabor himself:
You don’t want to leave your users feeling stupid, in the sense that they did something wrong, you want them to fill empowered and you want them to feel like your application is well built and it considered them whenever you were building it. Users expect a reliable experience with no surprises.