Support Forum
Search found 1707 matches
The difference is Scheduler Pro behind the scenes uses a scheduling engine. Which schedules events based on dependencies/constraints/calendars etc. While in basic Scheduler dependencies are just visual lines that do not affect event positions really. Ideally we need to be able to control how much an...
In the previous ExtJs version, this scenario would prompt with violation dialogue so this is what our users are accustomed to. Ah right. Yes, Ext Gantt has a special pseudo constraint handling such cases. Thank you for the feedback! I've made a feature request to port it: https://github.com/bryntum...
Hello, it allows me to proceed with the date change and it sets constraint type for Task B to SNET and Constraint Date = Task B Start Date. I was expecting a constraint violation dialogue since I am moving away from ASAP. This case does not produce a conflict at all. ASAP/ALAP is not a constraint re...
Hello, Please provide a runnable test case otherwise we can only guess what happens. So far I have only few questions on the code off the top of my head: What's the point of the 1st forEach loop if you anyway assign intervals after it? intervals.forEach(interval => { let nonWorkingDay = nonWorkingDa...
Any chance to get a test case (or at steps how this can be reproduced on some of our demos) so we could reproduce/debug the issue?
Otherwise it's impossible to guess what happens I'm afraid.
Hello, MS Project still imports data and replaces commas with semicolons as far as I see. So it's not that critical. Yet I've made a feature request to replace commas on our side: https://github.com/bryntum/support/issues/8515 Best regards, Arcady PS You can also process resource names on your appli...
The issue is fixed by now. Yet it's worth mentioning that your demo application wouldn't notice assignment records appearance even with that fixed version. The reason is root level records are collapsed by default. I'd recommend adding a tree column to the view to have better understanding whether a...
Closed the ticket since it's trivial to reach both the view and its store:
new ResourceUtilization({
getBarText(datum) {
// view is ResourceUtilization instance
const view = this.owner;
// view.store is corresponding ResourceUtilizationStore instance
view.store For example, we have 3 tasks ("task-1", "task-2", "task-3"), the user deletes task "task-1" which causes 3 changes, 2 to update orderedParentIndex of "task-2" and "task-3", and third change to remove "task-1". All three requests ...