-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
strange behavior with timeRanges #29
Comments
Hello, I'm facing same issue when change view and have more than one timeRanges then only first timeRange object updated. Also I've try gantt.refreshTimeRanges(); but not success. Just reference below function call internal from lib
Please help me out any workaround. Thanks in advance. |
Interesting, I've just tried the demo with multiple time ranges and I did not experience any issues. Any chance you share the rest of your gantt configuration? |
Were there any errors in the console? I've fixed an error when time ranges get destroyed which could result in a stuck view. |
thanks @ANovokmet for quick reply I'm working on angular and svelte-gantt@3.0.4-beta version please check below attached demo link after upgrade latest version now it's working as expected (except one issue when build project then one error occur as below) investigate error then found node_modules/svelte-gantt/types/modules/table/tableHeader.d.ts file import { SvelteRow } from "src/core/row"; when I replace with import { SvelteRow } from "../../core/row"; then it's working fine Again thanks @ANovokmet |
@nitish-darji thanks for the heads up on this error, I'll be investigating it. |
Hello @nitish-darji, do you still experience this issue cause after some tests I can't reproduce it either with the current version ? |
No answer and not able to reproduce the bug described |
Hi,
I pass several timeRanges to the gantt:
The gantt first loads the timeRanges:
When I change the day, a timeRange is still there, even if it was the day before:
I would have expected the timeRanges to only be there on the defined days.
Thank you.
The text was updated successfully, but these errors were encountered: