Our state of the art Gantt chart


Post by sasha573 »

Thank you, Alex! Much appreciated.


Post by nickolay »

@sasha573 Hi, it seems the exception thrown in caused by the id duplication in the dependencies data:

            setDependencies([
                { id : 1, from : 11, to : 12 },
                { id : 2, from : 12, to : 21 },
                { id : 3, from : 21, to : 22 },
                { id : 4, from : 22, to : 23 },
                { id : 5, from : 23, to : 31 },
                { id : 5, from : 31, to : 32 }
            ]);

There shouldn't be an exception in this case of course and we'll be fixing this, in the meantime, you can check that there are no such id duplicates in the data.

Please let me know if that fixes the exception problem for you.


Post by nickolay »

I'm about the "effectiveCalendar" exception. The original exception from this thread seems not to be reproducible in the "inline-data.7z" test case. Any additional steps to reproduce it?

As about the

Hovewer, from the attached sample, if we reset existing calendar intervals, only the initially loaded non-working intervals are displayed on gantt

this is probably a duplicate of the https://github.com/bryntum/support/issues/5394 (also https://github.com/bryntum/support/issues/5602), I'll be checking that as well.


Post by sasha573 »

Hi Nickolay!
The issue is more with sync of calendar intervals.
During the first load the "Business" calendar has two intervals:

   intervals : [
                     {
                         recurrentStartDate : 'every weekday at 18:00',
                         recurrentEndDate   : 'every weekday at 19:00',
                         isWorking          : false
                     },
                     {
                         recurrentStartDate : 'every weekday at 22:00',
                         recurrentEndDate   : 'every weekday at 23:00',
                         isWorking          : false
                     }
                 ]

When we update data by clicking "Change data", the "Business" calendar is updated and we receive only one interval:

intervals : [
                    {
                        recurrentStartDate : 'every weekday at 18:00',
                        recurrentEndDate   : 'every weekday at 19:00',
                        isWorking          : false
                    },
                ]

Hovewer, the gantt still displays two initially loaded intervals. The same could be reproduced with the changed data on 'New calendar 2' where the interval time is changing hovewer is not updated on the gantt.


Post by sasha573 »

We would also like to implement the feature of adding the new non-working calendar interval directly from the gantt and with this sync issue, I'm afraid there could be a problem with displayng the newly created calendar event.
Morover, we've are struggling with disappering of non-working calendar events during scroll - https://github.com/bryntum/support/issues/5723
Maybe, you could have a look at this issue as well?


Post by nickolay »

Yes, I'm checking the interval rendering updates. However the thrown exceptions have higher priority since they completely break the workflow for the users. Any additional information on the exception you mentioned in the beginning of the post?


Post by sasha573 »

Hi Nikolay!
I've managed to recreate the initial error. Please find attached the updated test case.
To recreate please load 3 machines, change veiw preset to hour, then zoom to fit and back to hour preset.
I'm catching the following error in console.

Capture.PNG
Capture.PNG (26.15 KiB) Viewed 196 times
Attachments
inline-data-zoom.7z
(1.73 MiB) Downloaded 22 times

Post by mats »

Call stack looks not purely Bryntum, what's "getPriorityField"?


Post by sasha573 »

As far as I can see it's a part of CalendarIntervalMixin


Post by mats »

Oops, had the wrong file filter enabled - thanks! We'll investigate.


Post Reply