I have a 3D graph built automatically; depending on the magnitudes of the datapoints, the vertical axes are scaled and the units in the axis label updated. The scaling is done with these two commands;
TransSurfaceG!layer1.z2.label.divideBy=1.000000E-3;
TransSurfaceG!layer1.z.label.divideBy=1.000000E-3;
where TransSurfaceG is the plot I'm using to demonstrate it; it can be downloaded by FTP from the "pub" directory on elecmigr.lancs.ac.uk.
These commands rescale the vertical, as expected. However, they also rescale the temperature axis, and I have to issue the command
TransSurfaceG!layer1.x.label.divideBy=1;
This has worked fine so far. However, the plots are now rotated programmatically to show the surface well regardless of the direction of the slope. This means that it's unknown whether the visible temperature axis is x1 or x2. Fixing both changes the visible z axis, thus breaking the scaling.
There seems to be some bizarre interaction between the x and the z axes, which so far I've bodged around. Rather than me increasing the complexity of the bodges, what's actually going on? Is this an Origin bug? If so it's been here unreported since at least v4. If not, what am I doing wrong?
On a related note, when I saved the graph out as a single page to prepare the demonstration, the top plot appears to have become corrupted; when I load the graph into a new instance of Origin, the bottom plot (layer 1) is fine, but the top plot (layer 2) which should look similar appears to be represented as a series of discrete 2D plots across the page and off to th eleft and right some indeterminate distance. This isn't any great problem to me since I never save single graphs, but is something that could do with looking into!
p.s. ignore the incorrect time arrow- I've not finished the latest round of modifications 
