Our state of the art Gantt chart


Post by rdonahue6 »

We have renderer added for predecessor column as bellow:

 {
                            type: 'predecessor', sortable: false, width: 112,
                            renderer:
                                ({ record }) => {
                                    let predecessors = record.predecessors;
                                    if (predecessors.length) {
                                        var toBeRendered = new Array();
                                        for (const predecessor of predecessors) {
                                            let lag = predecessor.get('lag');
                                            let lagSymbol = parseInt(lag) >= 0 ? '+' : '';
                                            let display = predecessor.get('predTaskSeqNumber') + ':' + predecessor.get('DependencyType') + lagSymbol + lag + ' ' + predecessor.get('lagUnit');
                                            toBeRendered.push(display);
                                            // return display;
                                        }
                                        return toBeRendered.join(',');
                                    }
                                }
                        },

We are committing stores on data load as below :

 that.ganttView.project.dependencyStore.commit();
 that.ganttView.project.taskStore.commit();
 

All other data is showing correct without "dirty" however predecessor column shows red corner as dirty.
how to avoid this??

Attachments
predecessorRenderer.png
predecessorRenderer.png (15.36 KiB) Viewed 4586 times

Post by tasnim »

Hi there,

I've tried the steps you mentioned in this demo https://bryntum.com/examples/gantt/advanced, but couldn't reproduce the issue. What version are you on? Could you please try with the latest version and see if you can reproduce?

Best regards,
Tasnim

How to ask for help? Please read our Support Policy


Post by rdonahue6 »

We have Bryntum Gantt 6.3.2


Post by mats »

This is issue has been fixed in v7 afaik so easiest would be to upgrade to our latest version.


Post Reply