Yes, now that we know it's a wicked parameter, ways will be determined to move it on somehow, or at least give better control over it. Wayne On Tue, 12 Dec 2006, Justin Douglas wrote: > Yep that got it. See attached screenshots. > > Is there anyway we can chose that in a popup or have more direct control > over this parameter? > > Thanks, > > Justin > > > On 12/12/06, Wayne Boucher <[log in to unmask]> wrote: > > > > Hmmm, I'm wondering if this is related to a problem noticed here the other > > day. At some point I added something called extraPad into the file > > > > ccpnmr1.0/python/ccpnmr/analysis/WindowDraw.py > > > > (near the top of the class definition). This was something to do with > > being able to select peaks (whose centers are interpolated away from the > > planes). If you set that extraPad to 0 (from the 0.5), I would guess that > > the problem goes away. So I'll have to look at this extraPad again and > > see if both problems can be sorted in one go. (The extraPad also led to > > the problem of not being able to reduce the window to one plane.) > > > > Wayne > > > > On Mon, 11 Dec 2006, Justin Douglas wrote: > > > > > Hi Wayne, > > > > > > I'm having a strange problem with printing (exporting) planes of 3Ds and > > > 4Ds. I used the middle mouse button to shrink the depth of a plane > > > to equal 1 point and chose the plane I wanted. If I export it and try > > to > > > manipulate the postscript I notice the figure has some "echo" looking > > > feature. Like adjacent planes are sneaking in. I've checked and the > > width > > > or depth of the plane is equal to the hz/point so unless I'm missing > > > something I should see true 2Ds. > > > > > > I've attached a figure to demonstrate. > > > > > > Do you have any ideas on how to correct for this? Can I set the depth > > > manually? > > > > > > Thanks, > > > > > > Justin > > > > > >