Search found 12407 matches

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...

I don't believe we support this, how about adding a new field to your EventModel class that reads this (via dataSource)?

Are you looking to achieve one or more "frozen" rows as this demo shows? In 6.0, this is supported natively: https://bryntum.com/products/scheduler-next/examples/lock-rows/ If not and you want to continue using your current demo code, are you able to share a runnable small test case with u...

Then probably engaging with our Professional Services would be the best way forward. With 1-2h of paid work we could (hopefully) provide you with a backported fix for your version.

How do you mean? Did you upgrade to the new version?

Thanks for your feedback! For every "real" resource received by the server, we create a new resource row (lets call this a SecondaryResource), that should be hidden (that's why we want the rowHeight to be zero). You could also use filtering for this perhaps? https://github.com/bryntum/supp...