Premium support for our pure JavaScript UI components


Post by dcporter »

In the Scheduler Pro when an event with no constraint is moved or resized, a constraint of startnoearlierthan is applied to the event. Is there a way to prevent this?


Post by alex.l »

Hi dcporter,

We always need reasons to have event started in some specific date. If event has no dependencies or constraints, it will start with project's start date (In case of using default forward schedule direction). If there are dependencies, event start date will be calculated according to those constraints.
When you manually move an event on a TimeAxis, an algorithm applies constraints (reasons) to have that event in some specific date, independent of (or together with) dependencies. So, it applies constraint date.

Full description of events scheduling https://bryntum.com/docs/scheduler-pro/guide/engine/schedulerpro_events_scheduling

You could try to use another constraints, as example make your event manually scheduled https://bryntum.com/docs/scheduler-pro/api/SchedulerPro/model/EventModel#field-manuallyScheduled

Btw, I don't see any constraints applied after I resize an event. How exactly did you get constraint date applied after resizing?

All the best,
Alex


Post by dcporter »

I'm not too sure I understand. It is currently possible to initialize the scheduler with an event that has a startDate and an endDate with no constraint.

Look at your demo here: https://bryntum.com/examples/scheduler-pro/constraints/

There are events in this demo that do not yet have any constraints on them. So clearly it is possible for an event to exist without any constraints. If I can initialize an event with no constraints, why can I not continue to leave it with no constraints after I move it?


Post by alex.l »

When I said "constraints", I mean dependencies as well.
If event has no constraints, no dependencies, no parent tasks and calendars with non working intervals or other things that may affect on event, the event will always be starting with project's startDate.

Scheduling Engine by default using forward direction of the scheduling, this means events will be scheduled to be happen ASAP. It's fully described in the guide I mentioned https://bryntum.com/docs/scheduler-pro/guide/engine/schedulerpro_events_scheduling

This means, the event needs to have a reason why its startDate should not be changed by the Engine.

All the best,
Alex


Post Reply