From: Ethan A M. <sf...@us...> - 2018-04-27 19:12:15
|
On Friday, April 27, 2018 11:21:29 AM PDT Dima Kogan wrote: > Ethan A Merritt <sf...@us...> writes: > > > The stupid error I found was in code that only dealt with the x axis > > of the current plot (so either x or x2). > > Hmmm. I see a very outwardly-similar problem if I "set logscale y" > instead of "set logscale x" in that test script. Do you see it too? Yes I see it too. But there is no y axis fixup code analogous to the x axis fixup code, So there is not an analogous stupid error that I can fix with one line of code. Ethan > >> I can imagine that x2 and y2 axes are affected and maybe 3d axes. And > >> maybe other stuff. Handling x,y,x2,y2 should hit most of the use cases, > >> probably. > > > > A higher-level fix is required so that all axes are correctly re-evaluated > > on refresh. The difficulty comes from trying to handle both pure > > "replot/refresh" requests and zoom operations. > > Yeah. I think the auto-writeback logic proposed earlier is the more > complete way to do this. |