Discuss anything related to web development but no technical support questions


Post by dominicdolan »

When Renaming a split segment of a task through the right click task menu after comleting the name change and removing focus or hitting enter no change events are triggered and listing in the segments on events are all only to do with drag drop and resizing of segments so i cant trigger a save automatically when the user enters a name for a segment.

Have i missed this somewhere in the docs or is this some missing functionality?
every other form of change to any tasks or segment triggers on change events for me.


Post by marcio »

Hey dominicdolan,

Thanks for reaching out.

If you use the following snippet, it'll be triggered when the event segment is updated

project : {
      listeners: {
        change: (ev) => {
          console.log(ev);
        }
      },

https://bryntum.com/products/gantt/docs/api/Gantt/model/ProjectModel#event-change

Best regards,
Márcio


Post by nickolay »

@dominicdolan What version of our component do you use? IIRC we've fixed this issue recently, please try to reproduce with the latest code?


Post by dominicdolan »

marcio wrote: Tue Mar 05, 2024 11:48 pm

Hey dominicdolan,

Thanks for reaching out.

If you use the following snippet, it'll be triggered when the event segment is updated

project : {
      listeners: {
        change: (ev) => {
          console.log(ev);
        }
      },

https://bryntum.com/products/gantt/docs/api/Gantt/model/ProjectModel#event-change

as i stated in my original question the problem is that the Project listener change event is not being triggered by the rename of a segment, i may not have called out the event explicitly but i did state that "every other form of change to any tasks or segment triggers on change events for me."


Post by dominicdolan »

nickolay wrote: Wed Mar 06, 2024 7:13 am

@dominicdolan What version of our component do you use? IIRC we've fixed this issue recently, please try to reproduce with the latest code?

I am using version 5.3.1 and am not sure if we can safely upgrade to the latest version, what version was this fixed in?


Post by nickolay »

If I'm correct it was fixed in 5.6.5 as part of this ticket: https://github.com/bryntum/support/issues/8079


Post Reply