Thanks for reporting, we're tracking this issue at https://github.com/bryntum/support/issues/587
Zooming will be refactored soon to have much better performance.
Support Forum
Search found 12397 matches
Yes sure this should be quite easy to do with tools like Puppeteer on the server. You can simply call the export method from your automated script to produce the PDF.
Can you please provide us a full test case so we can inspect code?
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...