TimeSpanValue Parse

[pfleck]

TimeSpan.TryParse also tries to parse strings that do not satisfy the format exactly. In this case the results can be unexpected.

Seconds and minutes over 59, and hours over 23 are interpreted as days. Therefore, parsing "72:00:00" does not result in 72h = 3days, instead is treated as "72.00:00:00" = 72 days.

Although the view immediately updates the parsed value, one can easily overlook incorrectly parsed values.

This should be prohibited via validation error (see TimeSpan.TryParseExact).

[pfleck]

r14025 Use TimeSpan.TryParseExact to avoid parsing illegal strings, e.g "24:00:00" since h must be 0-23.

The format specifier "c" (invariant) is used because it's format matches our defined TimeSpan format pattern. See HeuristicLab.Data/FormatPatterns.cs and ​https://msdn.microsoft.com/en-us/library/ee372286(v=vs.110).aspx.

[gkronber]

Please use the same format string for ToString calls.

[pfleck]

r14034 Added format specifier for ToString calls.

Although the parameterless ToString already use the "c" format specifier (see ​here) I added format specifier for consistency.

[gkronber]

Ok thanks!

[mkommend]

r14080: Merged r14025, r14034 to stable.