Oh.....
....did I forget to mention that if WindowViewState is "list", add 3
to the horizontal adjustments?
I need another drink....
Regards,
Chuck(le)
P.S. Can't wait to see what happens when WindowViewState is "table'.....
On Nov 21, 2008, at 4:14 AM, Chuck Pelto wrote:
The 'Final Solution'...
....short of incinerating the computer.
$$WindowVert = Get ( WindowTop )
$$WindowHorz = Get ( WindowLeft )
$StatusArea = Get ( StatusAreaState )
$$AdjustVert = $$WindowVert + 22
$$AdjustHorz = $$WindowHorz + If ( $StatusArea = "Visible" ; 69 ; 0 )
Do the GetLayoutObjectAttribute and add the $$AdjustVert or $
$AdjustHorz accordingly.
SAKES!!!
It's enough to drive a man to drink.
Which reminds me...
...who was that guy at the 1997 FMP DevCon who said he did his best
work at 2 am after 7 scotches??!??!?
I'm wondering.....
Regards,
Chuck(le)
On Nov 21, 2008, at 3:42 AM, Chuck Pelto wrote:
Oh God!!!!
On Nov 21, 2008, at 3:33 AM, Chuck Pelto wrote:
Addendum:
On Nov 21, 2008, at 2:55 AM, Chuck Pelto wrote:
I'm working with this ScriptMaker call and getting 'odd' results
when I try to get the coordinates of an object in a layout.
Whereas the Object Info palette says one thing for left-top-
right-bottom of the object, the GetLayoutObjectAttribute calls
say something markedly different for the very same object, as
the object is 'highlighted' by a dark outline while being
addressed by the script.
Is this a bug? Or an undocumented 'feature'?
What it is is just totally fouled-up, as far as I can see.
The offset of what GetLayoutObjectAttribute gives different from
the Object Info palette OR the DDR report is +32 pixels
vertically. It is, now get this....+50 pixels horizontally if the
Status Area is hidden and +119 if it is visible.
WHO on God's Green Earth DID THIS? And is there a method to this
madness?
And if you change the position of the database window....
...guess what....
...three guesses. First two don't count....
