> -----Original Message-----
> From: Gary Rathbone [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, December 09, 1999 9:19 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Shared Text and Shared Scripts
>
>
> Gary Rathbone Wrote :
>
> (snip)
> >>So, is there anyway to define different scripts to
> background fields
> >>? Or is the whole point that you can't or shouldn't ?
Gary, the problem is that there is really only one field there; it just
shows different text on each card. So the field can only have one script.
What your script is doing is setting the script of the one field 12 times,
and when it's done, the field's script retains the last setting.
> Peter Reid Replied :
>
> >I'd be tempted to have a single generic script for all the
> fields. If
> >each card contains a field which has a unique card number in it
> >(assuming I understand you correctly), then simply use this value
> >within the field scripts:
> >
> >on mouseUp
> > go cd (field "CardNo") of wd "Day"
> >end mouseUp
> >
> >Peter
>
> Thanks. The number stored in the field actually has no direct
> relationship to the number of the card in the separate window
> to which the field is linked. So I can't use a generic script.
As Peter suggested, if you use a variable in the field script to represent
the destination card number, you should be OK. I don't know how you
determine the destination card, but if it can't be described by a generic
variable expression (e.g., "the number of this cd + 1") then you could set a
custom property on each card indicating the destination card for when the
field is clicked. Then the field script could read
on mouseUp
go cd (the destinationCard of this cd)
end mouseUp
> I think my issue here is developing a Metacard project
> without full understanding of the Metacard
> language/environment. But, hey, I guess its the best way to
> learn...... isn't it ?
Yes, with a little help from the list!
Hope this helps!
Marni
----------------------------------------------------------------------------
--------------------
The views and opinions expressed in this email message are the sender's
own, and do not necessarily represent the views and opinions of Summit
Systems Inc.
