Hello all,
A short note about the check routine in Win-Digipet.
We always get the message after a new version:
"There are a lot of error messages since the update. What's that all about? They didn't exist before! My project always ran without errors.
"Position statement" on this:
Irony on
Of course, with every update we simply invent a few new error messages to annoy the user/so that it doesn't get boring.
Irony off
No, joking aside.
There are basically two main reasons for new messages:
1. the messages are the process of "lifelong" learning for all of us.
After all, we help users with minor and major problems on a virtually daily basis.
There are often cases where we discover a (problematic) (mis)configuration in the project. Often there are cases where there are no problems at all at first, but maybe in the course of time in certain constellations. And then we very often hear "why didn't WDP tell me that". Well, why...because we are also human and simply did not expect or could not imagine some things. But when we have "learned" something like that, we naturally want to protect all other users from such traps and there are new tests in the programme.
2. even if we try to avoid it... New functions in new programme versions sometimes simply need additional input that WDP did not need before. The programme has a long history of development and some real innovations simply require more input.
But:
It is never intended to annoy anyone with such messages or to burden you useless work. In the developer/beta circle, every new test message is debated and it is discussed again and again whether a message is more confusing or more helpful.
A final note:
Please also note that WDP distinguishes between error messages, warnings and info messages in the check routine. This is also often forgotten. A warning is not the same as an error. And an information message is even less so. There are cases where a warning is justified, but does not necessarily lead to a problem. An error, on the other hand, is very likely to lead to a problem (at least in the long run).
Regards
Markus Herzog
