Ivar Christopher

Option to turn on/off all plot titles. Ivar On Sat, 14 Oct 2023, Ivar Christopher wrote: On the topic of time axes, there needs to be some kind of explicit binding of all the non-visible time axes to the visible one. I'm always paranoid that one of the non-visble ones could get in a weird state where it's actually showing a different time range (it's happened...). I'll ponder other things for this dialog... Ta, Ivar On Sat, 14 Oct 2023, Jeremy Faden wrote: Fix layout should also automatically add...

On the topic of time axes, there needs to be some kind of explicit binding of all the non-visible time axes to the visible one. I'm always paranoid that one of the non-visble ones could get in a weird state where it's actually showing a different time range (it's happened...). I'll ponder other things for this dialog... Ta, Ivar On Sat, 14 Oct 2023, Jeremy Faden wrote: Fix layout should also automatically add a time axis at the bottom, or make this easy to do. I often see where people loose their...

Hi Jeremy, Yes, I very much agree that it would be nice (and good for newer users) to have both of these types of operations be more obvious and accessible. Ta, Ivar On Thu, 22 Jul 2021, Jeremy Faden wrote: Karate chop script: https://github.com/autoplot/dev/blob/master/demos/2019/20191108/karateChop.jy Add hidden plot is right-click on the layout tab's plots window, then Canvas->"Add hidden plot". [feature-requests:#750] Need operators for slicing stack into two columns and joining two plots into...

Jeremy, I don't really have a stake in this either way, but just to provide a counter-example: Suppose we have two people collaboratively working with a large data set. They both have the data set installed locally, but with different absolute path structures, but the same relative path structure from their respective working directories. In such a case, they would want to be sharing .vaps that worked seamlessly for both, but would not want to be schlepping data back and forth. Just a gedanken experiment--no...

I think I'm neutral on this, on balance. I like the idea of a well-documented way to access these commonly-used properties. But, on the other hand, I've spent several years training myself to think in the QDataSet world, so I'm relatively comfortable with, and almost competent at, using the existing accessors. I think it's a good idea to have a simple (and again--well-documented) interface for these properties for science users to use. I'm just not sure how quickly I'd shift to using them.

atan2() needs documentation tweak

User-set cache location reset to default by itself

Show depend_? data in Display Data dialog