Hi Sudhanshu,
Syncfusion Greetings.
We have validated this issue and hence this issue can be overcome by setting the delayUpdate(base property) as true in the schedule.
The root cause for this issue is that the react DOM render is calling twice when we call the setstate and hence Schedule React and template renders simultaneously. So we need have provided this property to overcome this type of issues.
Kindly try the sample and if the issue persists, try to reproduce the error in a sample and revert else share your code example/runnable sample (if possible) to serve you better.
Regards,
M.Vinitha devi
Hi Vinitha,
I am having a similar problem. The scheduler component flickers whenever I do a backend operation. I have a GraphQL server as backend, but the datasource of Scheduler is not directly linked to the data fetched from server. Is it possible to connect datasource to the GraphQL server? Also, I see the scheduler comp flickering whenever I try to send an operation to the backend. I am not updating the scheduler with results from the backend, but the scheduler still flickers. Is it the normal behavior for scheduler? To be precise, when does the scheduler component? I am thinking it flickers when there is a change to state or props of the parent component. I am not doing any change to state or props of parent component, but scheduler still flickers/refreshes. Please help me with this issue.
Thanks,
Prahal