Bug #737
- Fixed bug #737, which allows wait dates after due dates, but provides a warning (thanks to Arkady Grudzinsky).
This commit is contained in:
@@ -419,9 +419,9 @@
|
||||
#define STRING_TASK_VALID_ENTRY "A task must have an entry timestamp."
|
||||
#define STRING_TASK_VALID_DESC "A task must have a description."
|
||||
#define STRING_TASK_VALID_BLANK "Cannot add a task that is blank."
|
||||
#define STRING_TASK_VALID_WAIT "A 'wait' date must be before a 'due' date."
|
||||
#define STRING_TASK_VALID_START "A 'start' date must be after an 'entry' date."
|
||||
#define STRING_TASK_VALID_END "An 'end' date must be after an 'entry' date."
|
||||
#define STRING_TASK_VALID_WAIT "Warning: You have specified a 'wait' date that is after the 'due' date."
|
||||
#define STRING_TASK_VALID_START "Warning: You have specified a 'start' date that is before the 'entry' date."
|
||||
#define STRING_TASK_VALID_END "Warning: You have specified an 'end' date that is before the 'entry' date."
|
||||
#define STRING_TASK_VALID_REC_DUE "A recurring task must also have a 'due' date."
|
||||
#define STRING_TASK_VALID_UNTIL "Only recurring tasks may have an 'until' date."
|
||||
#define STRING_TASK_VALID_RECUR "The recurrence value '{1}' is not valid."
|
||||
|
||||
Reference in New Issue
Block a user