Date Constraint Resolution Problem

Bug Reports
#1

Platform & OS Version

Platform: Windows
OS Version: 11
OS Language Setting: British English

App Version

Version: 3.2.6
Application Shell: 3.2.6

Problem Description + Screenshots

If events are created in the Narrative pane, linking them through date constraints appears to fail thereafter.
The only way to fix the problem seems to be to manually move the linked event to a suitable date. After doing so, the linked event will move normally if the ‘source’ event is moved.

Steps to reproduce

Create a new file (fiction or whatever else has Narrative). This has also been shown to work adding events to an existing Narrative timeline.
Go to the narrative and create two events.
On the ‘source’ event, select the Constraints tab in the detail window.
Create a link to the second event. Set ‘Start equals end of’ the source event.
This will immediately result in a constraint error.
If you click ‘Resolve,’ asking it to move the selected event does nothing.

Note: the events will have no dates at this point, so I can see why there might be an issue.

Give the source event a start and end date.
Attempt to resolve the issue. (Again, nothing moves.)
Set the start of event 1 to the end of event 2.
The constraint error is now resolved and the constraint will work automatically.

Any relevant files?

Tidy Up

#2

Hi Niall,
Thanks for the bug report.

We have been able to reproduce the behaviour you describe, and will investigate and implement a fix shortly.

As you point out, there isn’t really anything sensible we can do to resolve the “violation” when both items don’t have dates. We can either leave it as a “violation” but disable the Resolve button in that situation, or choose not to highlight it as a violation until one or both of the items have dates instead.

Thanks,
Matt

#3

Well, there is a ‘resolution’ which is to remove the constraint, so the button’s still useful.

The second part, where a date has been added and it still won’t resolve, is more where I was concerned.