Can you please provide us a full test case so we can inspect code?
Support Forum
Search found 12395 matches
Sure, that'd be easy to do with a custom eventRenderer (or taskRenderer in Gantt) which lets you output any HTML markup. https://bryntum.com/products/scheduler/examples/custom-event-rendering/
Sounds strange, any chance you can upload a small test case to us?
Ok so problem solved?
Sounds like you have not used "id" for your events, then it will be treated as a new event and we'll send it to backend to be persisted. Have a look at the data you load for the events? Please feel free to post here too if you'd like us to review.
Just noticed this now, it's better you post in our forums about these issues as we do not monitor Github support repo for changes from external members. We'll investigate!
A task can have multiple predecessors each with different dependency type + Lag so this should not be an issue. Can you please elaborate a bit more on what you are not finding in our Scheduler Pro product?
Is it normal that you seem to have a jest log as part of the build ? Furthermore, if some tests are executed, it seems that they're not well handled. Do you run Jest tests as part of your build? I wonder if the heavy trial obfuscation might be a factor too? We haven't heard of similar slow build ti...
Can you please share how you would like it to look?
Any chance we can get a small test case so we can try to reproduce this locally?