>The issue is AutoAxes getting something with 3d positions. I figured it was Ribbon, not knowing about Translate in your network.
> If you had taken the Translate out and left Ribbon the way it was, the problem would have still been there. > I suppose the 3d positions could wreak havok somewhere else, but I did do this, and there was no apparent problem with the axes. But there was a problem with ribbon because it was not visible. >Why do you need Translate? Is it because you have coincident objects and want to have one visible over another? If so, do you know about fuzz? This allows you to assign visible priority to coincident objects. Use the Options module to assign it. The attribute is "fuzz" and you give it a numeric value. The higher the number, the greater priority compared to >other objects at the same location. I used Translate because Describe told me that the ribbon was a surface which if planar and aligned along the viewpoint will not be visible, and that it must be moved off-axis. Translate did make it appear. Maybe something else is better. Someone else just posted another mention of Fuzz. I don't see it here - is it a sample macro ? I assume if it puts the line on top of the rest of the plot, that line will have the added benefit of being visible, too ? :-) Sharon Gibson <[EMAIL PROTECTED]>@opendx.watson.ibm.com on 10/24/2001 03:03:09 PM Please respond to [email protected] Sent by: [EMAIL PROTECTED] To: [email protected] cc: Subject: Re: [opendx-users] AutoAxes Thanks anyway, but my plot is the same regardless of this trick (and the ribbon is still a surface). But in fooling with it, I discovered that my use of Translate may have been the thing messing the axes up. I cut out any translation in the z dimension, i.e. [.0001 .0001 0], and everything plots fine. Without Translate, the Ribbon line does not appear, (but the axes are OK !). --- Forwarded mail from [email protected] Subject: Re: [opendx-users] AutoAxes To: [email protected] From: "Lloyd A Treinish" <[EMAIL PROTECTED]> Date: Wed, 24 Oct 2001 08:27:45 -0400 Reply-To: [email protected] Ribbon creates triangles in 3d even if the input data are 2d (a feature). Its z-component is telling AutoAxes to do what you don't want. Try the following to remedy the situation: Ribbon | Remove(, "normals") | Mark (,"positions") | Compute ([a.x, a.y]) | Unmark | Sharon Gibson <[EMAIL PROTECTED]>@opendx.watson.ibm.com on 10/23/2001 03:19:53 PM Please respond to [email protected] Sent by: [EMAIL PROTECTED] To: [email protected] cc: Subject: [opendx-users] AutoAxes I am trying to display a colored field with 2-d positions in combination with a line created by the Ribbon macro, then framing the result using AutoAxes. AutoAxes works fine on just the field or just the line, but when I combine the two items the axis tick marks jump from primary x and y (left/bottom) axes to secondary x and y (right/top). Also, the axes labels are now covered up by the ticks. I see that the line (Ribbon) is really a surface, and although it displays OK, I'm wondering if that somehow messes up the axes ? --- End of forwarded mail from [email protected]
