Search found 3268 matches

You can get the element from the corresponding property: https://www.bryntum.com/docs/scheduler/#Core/widget/Button#property-element oEditEditor.widgetMap.saveButton.element Also you can trigger click handler by firing the click event: https://www.bryntum.com/docs/scheduler/#Core/widget/Button#funct...

Please provide more details of what you're going to do there. Better to interact with the data in the listeners fired when you click save button. There is no public API to trigger save.

Then you were right using the beforeTaskEditShow listener.

No need to hide it in CSS, you can filter out it from the store and the UI will be refreshed. For example, you can define filter as an object: id = gantt.taskStore.last.id gantt.taskStore.filter({ id : 'last-task', property : 'id', operator : '!=', value : id }) or as a function: gantt.taskStore.fil...
Please try the code online: https://bryntum.com/examples/scheduler/tree/ scheduler.resourceStore.removeAll() scheduler.resourceStore.rootNode.appendChild([ { id: '44b3b610-b455-48b5-a738-6370cec57cd1', name: 'r1', children: false, }, { id: '745b7453-4a01-4ccc-94a0-15925895f369', name: 'r2', children...
Hello, I've checked your testcase. The problem is not related to the custom tooltip. The way you implemented the editor is not valid. Please do the following instead: taskEdit : { items : { customTab : { items : { myNameField : { label : 'Name', name : 'name', type : 'text' } } }, generalTab : false...
When you change data in the task store, the engine propagates changes and recalculates values asynchronously. To make sure the propagation is done and you set the dates after it's completed, you can trigger the propagation manually: https://www.bryntum.com/docs/gantt/#guides/project_data.md#triggeri...
So you have a grid of resources at the right, and you have a scheduler which shows resources at the left. And you want to populate the scheduler resources by moving resources from the grid on the right to the resource list on the left. Is that correct? There is no such example, but it should be easy...

Thanks for the testcase. Your issue is reproducible. I've updated the ticket above. We will try to get that fixed. Stay tuned!

You can disable EventEdit feature completely by setting it to "false". This will also remove the item from the context menu. eventEditFeature = {false} If you disable the editEvent item in EventMenu, the editor is available and can be opened by double click or programmatically: eventMenuFeature = {{...