Skip to content

Comment on The Good, the Bad and the GUIparent

Comments

I don't understand why its usual to assume that the only two choices are

  * show N/A everywhere
  * silently ignore sources of potential errors.
Why not make the calculation while adding a visual cue (e.g. a yellow or red indicator in the corner) that marks the field as tainted? Now the users get to decide whether they want to investigate or ignore that.

You mean like Excel actually does? http://i.imgur.com/kMPKnqO.png

Does that propagate, or is it only one hop?

Yes.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.