Search found 2087 matches

Thank you very much for pointing this out. The problem can be alleviated in a custom renderer, for example: eventRenderer({eventRecord}) { return eventRecord.isMilestone ? '' : eventRecord.name }, however, this would hide all milestones if the logic is not made more clever. I have created a ticket t...

It can be achieved by setting "Manually Scheduled" of "Sprint 1 (to start)" task to true and then you can drag it where you want. As long as it is scheduled by the engine it cannot start earlier than its ancestor finishes.

Screen Shot 2021-10-01 at 08.55.33.png
Screen Shot 2021-10-01 at 08.55.33.png (98.57 KiB) Viewed 410 times
[editable]="false"

will work. editable property expects a Boolean, not string.

There should not be any performance issue with 500 events. We have a big dataset demo where we can have 10000 events with 1000 resources and the scheduler is still very fast. Would you please explain in more details, possibly with screenshots, code snippets of configuration and versions how the Sche...
I'm afraid the error stack is not useful – we do not want to guess what could be wrong. Post please a simplest possible runnable showcase that would demonstrate the error. That is a code that we can drop somewhere on the disk and actually run (npm run serve), load the data and see the problem. We wi...
There is nothing obvious that would be wrong in your code and there was no breaking change in our code since 4.1.x in this area (https://www.bryntum.com/products/scheduler/changelog/). Ideally, we would be able to reproduce it ourselves in a runnable showcase. Meanwhile, you can try to debug it your...

It is a bug; I have created an issue here: https://github.com/bryntum/support/issues/3465

Thank you for reporting.

Yes, the problem is most likely caused by removing the TimeAxis column and re-adding it later. That is somewhat unusual approach; what are you trying to achieve? Can you elaborate?

Setting that option to true alone would not trigger the error because then this demo https://bryntum.com/examples/scheduler/infinite-scroll/ would not work. Therefore, we need your case to sort out what's wrong.

Well, you are giving the scheduling engine an impossible task: "Engine, you have no dates, no durations, yet, schedule these events!" Truth is that the engine should not crash but give a console log or a popup (this feature will come in a later version), nevertheless, such data cannot be u...