-
Notifications
You must be signed in to change notification settings - Fork 528
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
Linked Axes #109
Comments
I like it. |
I also like this idea. That would certainly be a unique and useful feature. |
I implemented this by wrapping One can define in the So to share X axis one can write in this manner if (ImPlot::BeginSubPlot("X Shared", ImSubPlot_ShareAxisX)) {
if (ImPlot::BeginPlot("Plot A")) {
...
ImPlot::EndPlot();
}
if (ImPlot::BeginPlot("Plot B")) {
...
ImPlot::EndPlot();
}
ImPlot::EndSubPlot();
}
|
I like how generic the original proposed solution is, e.g. I can have linked plots in separate windows, or separated by non-linked plots. |
I like @epezent solution; in my applications I will probably “link” always x-axis and never y-axis (do you need up to 3 of ymin/ymax !?) I don’t like the name “link”, i will use synchronized or “sync” but this is definitely not a big deal for me. |
I have this working in the I like this system because:
|
Great! |
Great! It behaves like this because the drag operation is passing from one plot to the next or because it’s kept active in plot where it starts? |
The latter |
I was wondering to close PR #98 but not yet ... |
Merged! |
I'm considering an axis linking system so that drag on one plot will cause another plot to drag (see #53 (comment) and #94 (comment)). It is currently possible by exploiting
GetPlotLimits
andSetNextPlotLimts
, but setting up a bidirectional system is more difficult.Implementation details aside, what do folks think of something like this:
The pointer values will be used to set the next plot limits, and if any drag input is taken, it will update them accordingly so the changes can propagate to other plots. NULL could be passed for axes not linked. I haven't thought it out completely, but this is the most flexible and elegant solution I can come up with for now.
@PeterJohnson, @ozlb ...thoughts?
The text was updated successfully, but these errors were encountered: