Search found 2325 matches

Persisted data is the data you are loading (assuming it comes from some persistent data storage, like database). In this case, the persisted data is different from the data with scheduling logic applied - thus the visual "jump" happens.

Hello,

What exactly is not clear?

Hello, please provide access to your system again and the detailed steps how to reproduce the problem.

Sorry, its very hard to answer anything useful w/o being able to reproduce the problem. Very probably its something in your webserver setup, to which we obviously don't have access. Try googling for the similar errors perhaps.

Hello,

The fix was merged to our repo, it will be available in the tomorrow nightly or in the 5.5.3 release. To activate the fix, you will need to enable the adjustDurationToDST option in the project like this:

new Scheduler({
    project : { adjustDurationToDST : true }
}) 

That would be the safest, our alphas passes through the same automated quality control though, so you can try it too already.

This is a breaking change, so it is in the 5.6.0 branch (already available in the 5.6.0-alpha release)

Hi Rayudu. Unfortunately not much can be done here. You are rendering 5 years in daily resolution, which means a lot of task non-working time elements will be rendered. I've checked and for initial load there are 400 non-working time elements ( document.querySelectorAll('.b-tasknonworkingtime') ). O...

@gorakh.nath Hi. Can you please provide the localization information that lead to the

L{descriptionTpl}

message in the popup? Preferably as a runnable test case. We'll investigate the localization problem.

As about the reason why this popup appears - see the previous message by Arcady.

@dwr Hi, please see my reply in the ticket.