-
Notifications
You must be signed in to change notification settings - Fork 5
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
Flip axes programmatically and turn off interactive flipping #19
Comments
Looking at the source code from parcoords here, it looks like the syntax should be I think this functionality is hard-coded in parcoords as an "on-click" event (it's present even in our most basic examples), so I don't know that we actually have the power to disable it right now. This might be a question and potential request for our friends at parcoords. |
Thanks! For some reason It's okay if we can't disable the "on-click" flipping, I doubt many users will even know the flipping feature exists if we don't advertise it. Agreed though. There could definitely be some improvements on the Parcoords end. |
Welp. It turns out that when I use |
Classic. Does it break all brushes or just linked brushes? In either case, could you provide a brief example? I'll put this at the top of my list and also reach out to the parcoords team about providing the option to make flipping non-interactive. |
Update: In parcoords, the correct syntax to flip one or more axes is The issue with polylines disappearing on flipped axes is tracked in BigFatDog/parcoords-es#60. Sometime soon, I'll submit a PR to parcoords making interactive flipping configurable; similar to how |
@joshhjacobson, do you know how to flip axes in Parcoords without a mouse click? I can't figure out how to do it programmatically, only how to do it by clicking on the axes.
Also, do you know if there is a way to turnoff interactive flipping of axes? I want to put a preferred direction arrow in (and therefore, don't want the user to be able to mess with the axis orientation).
The text was updated successfully, but these errors were encountered: