View Revisions: Issue #4
| Summary | 0000004: config readers don't report invalid numerical parameters | ||
|---|---|---|---|
| Revision | 2017-02-01 20:37 by mtruesdell | ||
| Description | Right now config error are only visible in the log file. It is causing config line errors to be overlooked. For example any value other than an exact match can cause a bad configuration. I was going to wait until there is a GUI config but I'm not sure I can at this point as it will take too long. Use notepad to display log - will need a confirmation dialog on whether or not to continue. |
||
| Revision | 2017-04-07 18:10 by mtruesdell | ||
| Description | Need to check when booting program on a value other than 0 or 1 for binary numerical configuration and show the user a message. | ||
| Revision | 2017-02-01 20:37 by mtruesdell | ||
| Steps To Reproduce | set any "enabled" argument to something else and it will go to it's default value. | ||
| Revision | 2017-04-07 18:10 by mtruesdell | ||
| Steps To Reproduce | set any "enabled" argument (supposed to be only 0 or 1) to something else and it will go to it's default value. | ||
| Revision | 2017-04-07 18:18 by mtruesdell | ||
| Description | Need to check when booting program on a value other than 0 or 1 for binary numerical configuration. If it's wrong ignore it (will use default) and log it using invalidConfigHelper. | ||
