jflamy/owlcms4

explicit override for late changes

Closed this issue · 2 comments

changes after the 90s warning on 2:00 clock, or the 30s warning on a 1:00 clock are identified as in error,
The marshal is warned, but the need to use the "Ignore error" checkbox is no longer enforced.

Need to check if the other error conditions have that problem as well

Error condition is specific to the timing check. During to automated tests, the timing tests can be disabled. The code to disable them is also present in the interface so that timing validations don't take place while the object is being loaded before an actual edit has taken place There appears to be superfluous reset of this condition; taking it out seems to fix the problem.

Simple changed applied in 49.0.0-rc10