Hi, LAB1 = "FERRET (optimized) Ver.7.12"This data set does not have a "dataset title" so that label is empty. The "logo" with the Ferret version, date, etc, is drawn using moveable labels, so if we remove that, the label numbers change. The labels above the plot are drawn with moveable labels. yes? cancel mode logo yes? use levitus_climatology yes? shade/y=45 salt yes? sh symbol lab* LABX = "LONGITUDE"The label numbers change but the descriptive symbols LABNUM_DSET, LABNUM_Y, and so forth can always be used in scripts. In the terminology of PPLUS, the X label is the horizontal axis, Y is the vertical axis. These symbols are set on a SHADE/SET so they can be used to say, remove the dataset labels at the top and make the label in the upper left smaller shade/set/z=20 salt On 6/20/2017 12:22 PM, Marco van Hulten
wrote:
Op Tue, 20 Jun 2017 11:11:07 -0700 schreef William Kessler:I think PPL LISTSYM gives all the variables PPLUS knows about. It's a long list and not especially transparent (and only gives information after a plot is made), but might be useful. It will not do quite what you want because successive plots of different sizes/shapes will have different values of label numbers, axis lengths, etc (those will be numbered successively, so it could be useful for the first plot in a new Ferret session). But in general, as Ansley says it's better to specify the label height directly (LABSET for axis labels, LABEL for handmade ones). Then there's no ambiguity.Great, that's a useful command to check some things. I presume you cannot directly change these variables, or you are not supposed to? But to my issue. The variable returned by PPL LIST LABSET are not in the PPL LISTSYM output. I rather get some unconveniently formatted output. Can I save that in some way to a variable? I just want a jnl script to read the default font sizes, apply a scaling factor on them in LABSET, and plot them thus. In the end, there are just a couple of values \in {0.16, 0.12, 0.10} inch, so I could hard code them in my scripts: they are after all default values. But I thought there may be a more elegant way to do it. - Marco |