Skip to content
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

Dynamically modifying rollingMode with setOptions not working #939

Open
admc opened this issue Mar 1, 2021 · 0 comments · May be fixed by #1609
Open

Dynamically modifying rollingMode with setOptions not working #939

admc opened this issue Mar 1, 2021 · 0 comments · May be fixed by #1609
Labels
bug Something isn't working

Comments

@admc
Copy link

admc commented Mar 1, 2021

Using the latest version, 7.4.6.

When the selected date range ends with a date today or later, I want to be in rollingMode because the user experience makes a lot of sense, but if I select a date range in the past, I need to goto that range and display the data for those dates. Using setWindow to those new dates doesn't work, but neither does turning off rolling mode with setOptions, then calling setWindow. I also tried toggleRollingMode and that doesn't seem to work either.

Might be important to state that rollingMode works great when in the original options object, but seems unchangable after that.

I'm using cluster incase that makes a difference:
const options = { rollingMode: { follow: true, offset: 0.98, }, ... }
I want to dynamically turn off rollingMode.

instance.setOptions({ rollingMode: { follow: false, offset: 0.98, }, });

Let me know if theres anything else that would help to know!

Thanks for an incredibly library, this saved me enormous amounts of work, its too bad that both of the react wrappers are outdated and broken.

Cheers,
Adam

@mojoaxel mojoaxel added the bug Something isn't working label Mar 30, 2021
bpfoster added a commit to bpfoster/vis-timeline that referenced this issue Mar 30, 2023
Turning it on via setOptions() already worked but not the opposite.
fixes visjs#939
@bpfoster bpfoster linked a pull request Mar 30, 2023 that will close this issue
bpfoster added a commit to bpfoster/vis-timeline that referenced this issue Mar 30, 2023
Turning it on via setOptions() already worked but not the opposite.
fixes visjs#939
bpfoster added a commit to bpfoster/vis-timeline that referenced this issue Mar 30, 2023
Turning it on via setOptions() already worked but not the opposite.
fixes visjs#939
bpfoster added a commit to bpfoster/vis-timeline that referenced this issue Mar 30, 2023
Turning it on via setOptions() already worked but not the opposite.
fixes visjs#939
bpfoster added a commit to bpfoster/vis-timeline that referenced this issue Apr 4, 2023
Turning it on via setOptions() already worked but not the opposite.
fixes visjs#939
bpfoster added a commit to bpfoster/vis-timeline that referenced this issue Apr 4, 2023
Turning it on via setOptions() already worked but not the opposite.
fixes visjs#939
bpfoster added a commit to bpfoster/vis-timeline that referenced this issue Apr 4, 2023
Turning it on via setOptions() already worked but not the opposite.
fixes visjs#939
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants