[REACT] How to Navigate independently using shiftNext/shiftPrevious

[andrew.perera]

Hi Team,

As you know we use: https://bryntum.com/products/scheduler/examples/drag-between-schedulers/
structure and we have already utilised independent scrolling using - the 'removePartner' function.

However, if we use shiftNext() or shiftPrevious() for each scheduler instance they still move together.
Is this something we can do or would you suggest some option to get the following functionality?

grid.png (102.02 KiB) Viewed 828 times

As you can see we have a lock/unlock method with a padlock to activate independent scrolling using removePartner/addPartner

1. We want to introduce two arrows as per the picture so that we can navigate the time axis.
2. When we remove the partner scheduler we should be able to navigate only the bottom grid unit by unit in time axis by using arrows.

Appreciate your help.

[tasnim]

Hi,

Thanks for your report. We'll investigate it. Here is the ticket to track progress https://github.com/bryntum/support/issues/7045

All The Best,
Tasnim

[andrew.perera]

Hi Team, do we have any update on this?

[marcio]

Hey andrew.perera,

Unfortunately no updates, but I added a note to the ticket.

[andrew.perera]

Hi Team,
I'm not sure this is a new feature. I have noticed the bug label was removed. The expectation of removing a partner grid means schedulers should get independent control. It took about three months already.
Thanks.

[Animal]

The TimeAxis is shared between partnered schedulers.

This will have to be dynamically managed if partnership is broken then recreated.

https://github.com/bryntum/support/issues/7542

[andrew.perera]

Hi Team, any progress on this?

[marcio]

Hey andrew.perera,

We already have a PR for solving that issue, so it should be released soon.

[andrew.perera]

Hey Marcio, any update on this?

[ghulam.ghous]

Hi Andrew,

We have discussed this internally and increased the priority to high (you can see here https://github.com/bryntum/support/issues/7542). So it will be fixed soon as we tend to fix high priority tickets in a release timespan.

Regards,
Ghous