On 12/19/00 2:18 AM, "Paul Berkowitz" <[EMAIL PROTECTED]> wrote:
> On 12/19/00 1:34 AM, "Barry Wainwright" <[EMAIL PROTECTED]>
> wrote:
>
>> current messages
>> -- {incoming message id 679}
>>
>> first item of current messages
>> -- "Can't get item 1 of current messages"
>>
>> Set x to current messages
>> First item of x
>> -- incoming message id 679
>>
>> ???
>
>
> Lots and lots of Entourage, OE and some other applications are like this,
> Barry. When they're elements of the application itself, you have to
> evaluate them by setting them to variables or using 'get'.
>
> current messages
>
> on its own acts as if there is an implicit 'get', since there is no other
> object.
>
> In
>
> first item of current messages
>
> the only implicit 'get' is for 'item', the main object, and 'current
> messages' here doesn't get evaluated.
>
> This works:
>
> first item of (get current messages)
>
> as does (as you noticed)
>
> set x to current messages -- implies a 'get'
> first item of x
>
> You'll notice this with all the application elements, and you just get used
> to it after a while. Maybe Cal or Scott could explain it in more depth than
> I can, if you ask on one of the script lists. It's come up there before, in
> connection with various apps. And it's been that way in OE forever.
It is a limitation in Entourage's scripting support that's a bit difficult
to fix. It's something that's been on our list for a while, but we haven't
gotten to it. The work around is pretty easy once you figure out what's
going on.
Dan
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
To search the archives:
<http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
