Premium support for our pure JavaScript UI components


Post by victor palma »

We have a problem when try to activate criticalPaths feature.
Where it throws us the following error.
when this happens the gantt stays frozen, but if another feature is activated, the criticalPath does appear.

Attachments
image (1).png
image (1).png (186.99 KiB) Viewed 244 times

Post by arcady »

Can we have a test case to investigate? Or maybe steps how this can be reproduced on our demos?


Post by victor palma »

The versions are:

  • gantt: @bryntum/gantt”: “@4.1.0"

  • npm: 14.16.0

  • “vue”: “3.0.0"

  • “typescript”: “4.1.5"

  • “vite”: “2.2.4"

And the initial setup:

const columns = [
  {
    type: 'name',
    field: 'name',
    text: 'Nombre',
  },
  {
    type: 'date',
    field: 'startDate',
    text: 'Inicio',
  },
  {
    type: 'date',
    field: 'endDate',
    text: 'Termino',
  },
];
const tasksData = [
  {
    id: 1,
    name: 'Making ETA',
    startDate: '2021-05-01',
    duration: 5,
    baselines: [
      {
        startDate: '2021-05-01',
        endDate: '2017-05-07',
      },
    ],
  },
  {
    id: 2,
    name: 'Composing docs chapter 1',
    startDate: '2021-05-01',
    duration: 10,
  },
  {
    id: 3,
    name: 'Composing docs chapter 2',
    startDate: '2021-05-12',
    duration: 1,
  },
];
const dependenciesData = [{ id: 23, fromEvent: 2, toEvent: 3, type: 3 }];
this.ganttConfig = {
  project: {
    eventsData: tasksData,
    dependenciesData,
    syncDataOnLoad: true,
  },
  columns,
};

new Gantt({
  appendTo: 'bd_gantt',
  startDate: this.ganttConfig.startDate,
  endDate: this.ganttConfig.endDate,
  columns: this.ganttConfig.columns,
  project,
  autoHeight: this.autoHeight,
  features: {
    dependencies: {
      disabled: !this.useDependencies,
    },
    baselines: {
      disabled: !this.useBaseLines,
    },
    criticalPaths: {
      disabled: !this.useCriticalPaths,
    },
    taskDrag: {
      disabled: false,
    },
    timeRanges: {
      disabled: !this.useTimeRanges,
      showHeaderElements: true,
    },
  },
  taskRenderer({ taskRecord }: any) {
    return [
      {
        html: taskRecord.name,
        style: 'margin-bottom : 0.5em',
      },
    ];
  },
});

Post by arcady »

The code you provided looks correct and I cannot reproduce the issue. Yet I'm checking it on the latest Gantt (aka v4.1.4).
Have you tried your code with the Gantt v4.1.4?
If the issue is still reproducible for you with the latest version please pack and send us a runnable test case that we could debug to see what happens (please remove node_modules folder to reduce its size).


Post by victor palma »

arcady wrote:
Fri Jun 04, 2021 7:05 am

The code you provided looks correct and I cannot reproduce the issue. Yet I'm checking it on the latest Gantt (aka v4.1.4).
Have you tried your code with the Gantt v4.1.4?
If the issue is still reproducible for you with the latest version please pack and send us a runnable test case that we could debug to see what happens (please remove node_modules folder to reduce its size).

We tried version v4.1.4, but the problem remains the same.
We will send you a version of our code shortly.


Post by victor palma »

This is an example of our code.
https://github.com/iqbuild/bryntum-test


Post by victor palma »

We tried to recreate the implementatiin, but return another error (in image).
I attached the project for analysis

Attachments
gantt_vue.7z
(387.16 KiB) Downloaded 17 times
image (2).png
image (2).png (36.78 KiB) Viewed 199 times

Post by arcady »

Yes that's what we are seeing too. We are already checking the test case..


Post by victor palma »

arcady wrote:
Tue Jun 08, 2021 5:12 am

Yes that's what we are seeing too. We are already checking the test case..

Any results?


Post by arcady »

Still checking. Investigation of big datasets takes more time..


Post Reply