Thanks for sharing, all working as you want now?
Support Forum
Search found 12414 matches
Probably better to wait for the LockRows feature in 6.0, we'll try to support this case there. Did you try this out yet? https://bryntum.com/products/scheduler-next/examples/lock-rows/
see details below
Could you please share the full call stack?
That's not a simple thing to build in our world, at least not using the out of the box APIs. We have this ticket open which you can track: https://github.com/bryntum/support/issues/3274 As it's very few asking for it, it's unlikely we will implement it soon unless you are interested in a Feature Spo...
Thanks for pointing this out, just fixed it - will be part of the next release!
How can we reproduce this? Are you able to reproduce it in our online examples?
Are you setting destroyStores to true on your Gantt instance? https://bryntum.com/products/gantt/docs/api/Scheduler/data/mixin/ProjectConsumer#config-destroyStores
In SchedulerPro, you should use the project instead of the CrudManager. Does it work for you if you make this change? https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel For now i think I'll go with the regular Scheduler components. Those are included when buying a Pro...
Upon running the application, you will encounter an error logged in the console.
Can you please share the full stack trace?
No I'm not trying to achieve locked/frozen rows. I want to achieve multiple schedulers using a single CRUD Manager as implemented in the demo i linked above. Thanks for clarifying. Hard to say what it means, as the error is in the scheduling engine. Once we get something we can run, we should be ab...