Share the AppleScript? :)
--
Beverly Voth
mailto:[EMAIL PROTECTED]
tel:(606) 864-0041
--
On Nov 21, 2008, at 5:52 AM, Chuck Pelto <[EMAIL PROTECTED]> wrote:
On Nov 21, 2008, at 3:40 AM, Miki Eff wrote:
Just playing around with it a bit with the data viewer, it seems
that the bounds are relative to the entire screen and not to the
window of the current layout, where the origin (0, 0) could be
anywhere on the screen. The Object Info is relative to it's
layout's origin.
Since the window's orientation is also relative to the screen, I
suppose a simple subtraction would give you the real estate of the
window borders and status area if you are using it, if the absolute
position is necessary for your scripting purpose. Ah, I see you got
that in the followup post.
I suppose there is a method to the madness, whereas when scripting
window placement, you would want it relative to the screen. When
FMP is drawing a layout, it would want that layout to be rendered
in relation to its own origin.
Just curious, can I ask what is it that you are scripting using the
position attribute?
I'm working on an improvement over the crummy DDR.
There are a LOT of information missing, e.g., button and other
object names as applied in the Object Info palette, that I need in
order to streamline development.
I've developed an AppleScript to extract the data from the DDR and
drop it into an FMP database. The ScriptMaker then runs a script to
populate information that's available via the
GetLayoutObjectAttribute() call. The match-ups come via the object
coordinates in a given layout. The object name is then dropped into
the appropriate record in the FMP database.
I can then identify all the objects of importance in the newly
developed database, provide descriptive information and generate an
in-line users manual to support the end-users needs to know what to
do where.
Regards,
Chuck
