Sometimes code does become more like his, however. Like someone else commented already, it's far more common to store the states in a model. Often the way chang

Sometimes code does become more like his, however. Like someone else commented already, it's far more common to store the states in a model. Often the way changing one control would then enable a button that depends on it is that it would trigger an invalidate which would cause the rest of the UI to check the model again. I have seen this sort of code then become more like his when the invalidate step became too expensive, and what was invalidated or what was changing had to start getting specified. I admit it has only happened in games for me, though, where you often have super complex UI states and have to manage smooth frame rates.