Zandronum Chat on our Discord Server Get the latest version: 3.2
Source Code
My View | View Issues | Change Log | Roadmap | All Projects Issue Support Ranking | Rules | My Account
  

View Revisions: Issue #621 [ All Revisions ] [ Back to Issue ]
Summary 0000621: Improve the way config dialog box validates the config data
Revision 2011-11-11 20:23 by Zalewa
Description Currently, when Doomseeker detects invalid information in the config dialog box, the validation is performed after user presses OK and then a custom error information is displayed.

I propose to make following changes to validation mechanism:
[list]
[*] Validation should occur immediatelly after the data is inserted, or when user leaves the current config page, or when user presses either "OK" or "Apply" buttons.
[*] Validation should produce either errors or warnings. Errors will disallow user to save the configuration. Warnings will give an option to ignore them.
[*] Errors should be produced wherever Doomseeker can be 100% sure that the inserted data is incorrect.
[*] Warnings should be produced wherever inserted data might be incorrect. For example: a warning should be issued if user points a path in one of the game's configuration to a binary with odd name. For example user might specify that Skulltag's executable is "/bin/bash", which is most likely an error, but we can't say for sure that is not what was intended.
[*] Once an error/warning is issued, config box should immediately switch to the offending config page and visibly mark the offending variable with an icon. Hovering a mouse cursor over that icon should display a tooltip describing the error.
[/list]

Additional features:
[list]
[*] Validation could also occur when the configuration box is opened. This would help to detect potential configuration errors that were caused by external events. For example: removing a directory from filesystem will now render that directory invalid in WAD paths.
[/list]
Revision 2011-11-11 20:23 by Zalewa
Description Currently, when Doomseeker detects invalid information in the config dialog box, the validation is performed after user presses OK and then a custom error information is displayed.

I propose to make following changes to validation mechanism:
[list]
[*] Validation should occur immediatelly after the data is inserted, or when user leaves the current config page, or when user presses either "OK" or "Apply" buttons.
[*] Validation should produce either errors or warnings. Errors will disallow user to save the configuration. Warnings will give an option to ignore them.
[*] Errors should be produced wherever Doomseeker can be 100% sure that the inserted data is incorrect.
[*] Warnings should be produced wherever inserted data might be incorrect. For example: a warning should be issued if user points a path in one of the game's configuration to a binary with odd name. For example user might specify that Skulltag's executable is "/bin/bash", which is most likely an error, but we can't say for sure that is not what was intended.
[*] Once an error/warning is issued, config box should immediately switch to the offending config page and visibly mark the offending variable with an icon. Hovering a mouse cursor over that icon should display a tooltip describing the error.
[/list]

Additional features:
- Validation could also occur when the configuration box is opened. This would help to detect potential configuration errors that were caused by external events. For example: removing a directory from filesystem will now render that directory invalid in WAD paths.
Revision 2011-11-11 20:22 by Zalewa
Description Currently, when Doomseeker detects invalid information in the config dialog box, the validation is performed after user presses OK and then a custom error information is displayed.

I propose to make following changes to validation mechanism:
- Validation should occur immediatelly after the data is inserted, or when user leaves the current config page, or when user presses either "OK" or "Apply" buttons.
- Validation should produce either errors or warnings. Errors will disallow user to save the configuration. Warnings will give an option to ignore them.
- Errors should be produced wherever Doomseeker can be 100% sure that the inserted data is incorrect.
- Warnings should be produced wherever inserted data might be incorrect. For example: a warning should be issued if user points a path in one of the game's configuration to a binary with odd name. For example user might specify that Skulltag's executable is "/bin/bash", which is most likely an error, but we can't say for sure that is not what was intended.
- Once an error/warning is issued, config box should immediately switch to the offending config page and visibly mark the offending variable with an icon. Hovering a mouse cursor over that icon should display a tooltip describing the error.

Additional features:
- Validation could also occur when the configuration box is opened. This would help to detect potential configuration errors that were caused by external events. For example: removing a directory from filesystem will now render that directory invalid in WAD paths.

[list]
[*]Test
[/list]


  • test




Questions or other issues? Contact Us.

Links

Copyright © 2000 - 2025 MantisBT Team
Powered by Mantis Bugtracker