Something like this in your items
config:
// Remove default name field
name: false,
// Create your own field mapped to name
myNameField : { type : 'text', ref : 'name', name : 'name', label : 'My name' },
Something like this in your items
config:
// Remove default name field
name: false,
// Create your own field mapped to name
myNameField : { type : 'text', ref : 'name', name : 'name', label : 'My name' },
Hi,
Not sure I follow what you want to achieve, but you can both rearrange the built-in fields and add your own. More information here: https://bryntum.com/products/gantt/docs/guide/Gantt/customization/taskedit, and in this demo https://bryntum.com/products/gantt/examples/taskeditor/
Hi,
Not sure I follow what you want to achieve, but you can both rearrange the built-in fields and add your own. More information here: https://bryntum.com/products/gantt/docs/guide/Gantt/customization/taskedit, and in this demo https://bryntum.com/products/gantt/examples/taskeditor/
Hi,
from reading our sources it looks like you are correct, thanks for a clear and on-point report! Have opened a ticket on fixing it: https://github.com/bryntum/support/issues/9062
Hi,
thanks for reporting. It is an issue with the CSS for that specific demo, have opened a ticket on fixing it: https://github.com/bryntum/support/issues/9059
If you have a list of objects, I recommend trying a StoreDataField
. It will turn the list into records in a store, that can be manipulated as other records - leaving the record owning the field modified.
Docs here https://bryntum.com/products/schedulerpro/docs/api/Core/data/field/StoreDataField
If you have a list of objects, I recommend trying a StoreDataField
. It will turn the list into records in a store, that can be manipulated as other records - leaving the record owning the field modified.
Docs here https://bryntum.com/products/schedulerpro/docs/api/Core/data/field/StoreDataField
True, but I think it is as close as we can get to what you are asking for using the current API.
I have not tried it, but you could try subclassing ObjectDataField
, creating your own field type. And implement a serialize()
fn in it to only serialize it if a value was modified