Search found 6519 matches

Hi, Did you use group features? Which one? It's not clear from the screenshot. You could try schedulerPro.store.allRecords . Btw, here is a bunch of useful methods to work with tree. Please review the section Tree https://bryntum.com/products/schedulerpro/docs/api/Grid/feature/Tree#function-expandTo...

I don't see any z-index styling on the screenshot. Try to apply CSS style to your cell element to have z-index more than non working time element.

Hi,

We usually release every 1-3 weeks. We can't give you dates, but we plan to release 5.6.9 ASAP, already preparing branch.

Hi dmitrypromx, That's not relevant to the issue. Salesforce has own context and blocks most of default browser API in global context, we have to handle that. In your case, we need to have a look at the code you used. Please share a runnable test case if possible or at least code how did you load lo...

Hi himanshurjoshi,

UPDATE:

I removed my reply since my fix didn't work and Tasnim's ticket is valid.

Hi, Task has predecessor and should move backward/forward and also user can change LAG (-ve/+ve) that should move task accordingly. Task should move with its predecessor if user move predecessor task. There should be a reason why task should stay on the place you moved it. First thing might be a con...

Did it fix the problem?

Hi,

Yes, you need to add tree: true into your store config, in case you used store instance for your widget.
We could have a look at the code, if you' prepare a test case and steps how to run it and reproduce the issue.

Ok, I see. Did you try to change z-index for your custom class and for the container that you used to render your chart?

Hi,

I tested nonWorkingTime with our demo and I do not see that problem. Are you able to reproduce that in our demo? We need a runnable test case to conform a bug.

Screenshot is attached.

Screenshot 2024-04-08 at 13.30.01.png
Screenshot 2024-04-08 at 13.30.01.png (658.67 KiB) Viewed 168 times