Vladimir Ein
Vladimir Ein
This is just to document the fix I have (which I'm going to push in future).
A note to myself: this one is waiting for PR #2113 to be merged (to avoid conflicts).
> Is this because, the plot is not refreshed yet? Exactly. `get_axis_limits` retrieves the "actual" limits (`mvPlotAxisConfig::limits_actual`), which only gets updated when the plot is rendered. Until the next frame,...
I almost haven't used plots, but it might be that `get_axis_limits` also reflects changes when the user zooms and pans the plot. Not sure.
I've no idea why :) but clearly it was a design decision at some point.
The root cause is that `set_primary_window` overrides `window->configData.windowflags` entirely, instead of fixing just those of them that are needed for the primary window. Until this is fixed, @Tetane's workaround is...
Another side effect of `set_primary_window` is that it can modify _other_ windows, in particulary, by marking the window position as dirty. This affects positioning of modal windows: - By default,...
PR #2275 is going to fix this.
64 columns by 1000 rows is at least 64,000 widgets. DPG simply wasn't designed for such volumes of data. While I agree that things start getting pretty slow in DPG...
BTW you can't use multiprocessing (either directly or via joblib) because DPG in other processes won't have its internal structures. Moreover, DPG is designed in a way that only one...