Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Design mistake --- Closing --- Extended handling of "fail-unknown-thing" (fut) with hooks allowing this general code to ask for custom messaging. Directly from the parameter, indirectly from the validation type. Whose "validate" method is where "fail-unknown-thing" got called from. Which means that we have a possible alternative solution which does not go through such a convoluted circle: New convenience function, an extension of "fail-unknown-thing" which simply takes the custom message as a parameter. And we can write more functions of this type then, which take ranges, dicts, etc. and operate on these for rendering, or a possible user-choice to fix the bad value. Saving the current state before making a decision --- Trunk went forward with the alternate approach, see [3305575764]. |
|---|---|
| Timelines: | family | ancestors | x-fut-acceptable |
| Files: | files | file ages | folders |
| SHA1: |
86ce9388c1a27b495ca30e9c47beb969 |
| User & Date: | andreask 2015-06-26 21:58:26.590 |
| Original Comment: | Extended handling of "fail-unknown-thing" (fut) with hooks allowing this general code to ask for custom messaging. Directly from the parameter, indirectly from the validation type. Whose "validate" method is where "fail-unknown-thing" got called from. Which means that we have a possible alternate which does not such a convoluted circle: New convenience function, an extension of "fail-unknown-thing" which simply gets the custom message directly as a parameter. And we can do other functions of this type then, which take ranges, dicts, etc. and operate on these for rendering, or a possible user-choice to fix the bad value. Saving the current state before making a decision. |
Context
|
2015-06-26
| ||
| 21:58 | Design mistake --- Closing --- Extended handling of "fail-unknown-thing" (fut) with hooks allowing this general code to ask for custom messaging. Directly from the parameter, indirectly from the validation type. Whose "validate" method is where "fail-unknown-thing" got called from. Which means that we have a possible alternative solution which does not go through such a convoluted circle: New convenience function, an extension of "fail-unknown-thing" which simply takes the custom message as a parameter. And we can write more functions of this type then, which take ranges, dicts, etc. and operate on these for rendering, or a possible user-choice to fix the bad value. Saving the current state before making a decision --- Trunk went forward with the alternate approach, see [3305575764]. closed check-in: 86ce9388c1 user: andreask tags: x-fut-acceptable | |
|
2015-05-12
| ||
| 22:15 | config, color - Bump version numbers, due to their recent changes. check-in: 4f21251865 user: aku tags: trunk | |
Changes
Changes to parameter.tcl.
Changes to validate.tcl.
Changes to vcommon.tcl.