[Date Prev][Date Next]
[Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[New search]
To: Rick Quatro <frameexpert@xxxxxxxxxxxxxx>
Subject: Re: FrameScript Bug
From: Frank Elmore <elmsoft@xxxxxxxxxxxxxx>
Date: Thu, 22 Jul 1999 13:42:16 -0400
CC: Framers2 <framers@xxxxxxxxx>, Framers1 <Framers@xxxxxxxxxxxxxx>
References: <003101bed2c6$ccce9200$e8d8cdcf@carmen>
Sender: owner-framers@xxxxxxxxx
Hello, This is not actually a FrameScript bug. This is the way Adobe treats Sub Columns. Although a sub column belongs to a text frame, Frame treats its starting X and Y locations as if it were a separate object. Frank Elmore Project leader for FrameScript Rick Quatro wrote: > Hi Framers, > > I wanted to let you know of a FrameScript bug that is not fatal, but can be > annoying if you don't know about it. The Sub Column property SubCol.LocY is > supposed to be the offset from the top of the TEXT FRAME that contains the > subcolumn. Instead SubCol.LocY will give you the offset from the top of the > PAGE that contains the subcolumn. The property SubCol.LocX is also > incorrect; it is relative to the page instead of the text frame. > > If you need the actual offset from the top of the text frame, use this > instead: > > Set vSubColTrueLocY = vSubCol.LocY - vSubCol.ParentTextFrame.LocY; > > where vSubCol is a Sub Column object. > > If you need the actual offset from the left of the text frame, use this > instead: > > Set vSubColTrueLocX = vSubCol.LocX - vSubCol.ParentTextFrame.LocX; > > where vSubCol is a Sub Column object. > > Rick Quatro > Carmen Publishing > frameexpert@mindspring.com > FrameScript Information at http://www.mindspring.com/~frameexpert > > ** To unsubscribe, send a message to majordomo@omsys.com ** > ** with "unsubscribe framers" (no quotes) in the body. ** ** To unsubscribe, send a message to majordomo@omsys.com ** ** with "unsubscribe framers" (no quotes) in the body. **