On 6/30/13 8:42 PM, Geoff Canyon wrote:
In the email, item 2 is:
2. While every Type must be unique, a Type can be the same as the
Subsection it's in. This is the only non-unique exception.
In the file it says,
2. While every Type must be unique, a Type can be the same as a Subsection
within the same Section. This is the only non-unique exception.
which of those is correct? (hoping it's the first)
Sorry, I edited them at different times. At most, one line of a
subsection can have a type with the same name as its containing
subsection. I'm not quite sure which one of those two statements says
that. The first one, I think.
In these two lines:
AB MediumOrchid Gray100 Gray100|MULT|DIV
AB MediumOrchid Gray100 Gray100|MULT|DIV
The first line is okay. Its type matches its subsection, which is
allowed. The second line is not okay because every type name must be
unique. Either line could be wrong, but I'd probably flag the second one
as a duplicate type name.
In this line:
EF Chocolate1 LavenderBlush2 Gray100|COUNT|MINUS
The type would be okay if it were the only instance in the whole file.
Otherwise it's a duplicate from ID "AB".
Does that make sense?
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
