Our pure JavaScript Scheduler component


Post by deveshwaar »

Assume i have a component like this below which will get the events and resources from the redux store

  
console.log('@SchedulerEventsProjectModel'); const { schedulerEventsProjectRef } = useRmsGridInstance(); const { schedulerEvents, schedulerResources } = useSelector( selectAllUnallocatedTasksByContext ); useImperativeHandle(ref, () => schedulerEventsProjectRef.current); useEventProjectProcess(); return ( <BryntumSchedulerProProjectModel ref={schedulerEventsProjectRef} {...EventsProjectConfig} resources={schedulerResources} events={schedulerEvents} /> ); });

In our app, we have a function that filters the time axis to display only specific dates. When this filter is applied, the Redux store updates with new events, causing the component to re-render with the updated event data. However, after the update, the time axis shows the event timings incorrectly.

I believe the issue might be that the time calculations are not being handled properly during the update. It seems like I might need to perform an operation similar to commitAsync() to ensure the calculations complete correctly before the render.

Has anyone encountered a similar issue or have suggestions on how to address this?


Post by ghulam.ghous »

Please share more details, along with a small data set and the filters you are applying to timeAxis. Also share what is the current result and what should be the expected result. I believe if you are filtering the timeAxis, you should specify that time as non-working in the calendars and adjust it according to your requirements. Check the calendars guide here: https://bryntum.com/products/schedulerpro/docs/guide/SchedulerPro/basics/calendars


Post Reply