This issue introduces the notion of a Comprehensive & centralized design integrity checker. It is currently at the level of a concept and needs more thought and development before it can be considered as the basis for code changes. Specifically, the relationship to the current Alert facility should be examined. Simply extending the current Alert facility may be the best approach.
Conceptually, it should be possible to develop a single code module that can perform various tests to confirm that a design is trouble free. Potentially, there are multiple levels:
the necessary elements of the design data structures are present and well formed. See #440 & #855 for an example where this was not true. The design does not contain NaN values.
the design meets the validity tests associated with the Alert facility. The various severity levels (Err, Warn, Notice & Info) can be treated separately. Tests for No Free IV and Inverted (inconsistent) Constraints are in this category.
The design is (Not, Close to or Strictly) feasible.
This single code module can be invoked at various places to provide an additional level of alerting for the user. Specifically:
File menu operations (Open, Save, Save As, Import, Export)
Return from Search, Seek & Trade
Opening a catalog spring
The availability of such a comprehensive & centralized design integrity checker allows for another level of alerting. If the checker turns up no problem, the user sees nothing. If the checker turns up a minor problem, perhaps the user sees some words referring to the Alert facility appended to the message section of the resultTable section of the main page. A severe problem could produce a pop-up message. Perhaps the File : Save, Save As & Export functions could have a message integrated in their modal dialogs.
This issue introduces the notion of a Comprehensive & centralized design integrity checker. It is currently at the level of a concept and needs more thought and development before it can be considered as the basis for code changes. Specifically, the relationship to the current Alert facility should be examined. Simply extending the current Alert facility may be the best approach.
Conceptually, it should be possible to develop a single code module that can perform various tests to confirm that a design is trouble free. Potentially, there are multiple levels:
This single code module can be invoked at various places to provide an additional level of alerting for the user. Specifically:
The availability of such a comprehensive & centralized design integrity checker allows for another level of alerting. If the checker turns up no problem, the user sees nothing. If the checker turns up a minor problem, perhaps the user sees some words referring to the Alert facility appended to the message section of the resultTable section of the main page. A severe problem could produce a pop-up message. Perhaps the File : Save, Save As & Export functions could have a message integrated in their modal dialogs.