Code: Select all
put the abbrev id of me into tAbbrevRef
put the long id of me into tLongRef
put tAbbrevRef is tLongRef
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, LCMark
Code: Select all
put the abbrev id of me into tAbbrevRef
put the long id of me into tLongRef
put tAbbrevRef is tLongRef
Code: Select all
switch the controlType of <object ref>
case stack
...
Yes - I'd propose 'object' being the catch-all. I must confess I always thought 'object' would be fine for referring to faceless objects. They'd just be customprops+name+id+layer+script with no other properties. However, when we get 'open language' it might be that they wouldn't be of much use - as syntax wrapped arrays or something similar would probably work better.It seems to me that 'object' should be used here (and elsewhere) as a super class of everything much like control is for layers. It might be better to come up with another name for faceless objects so they can both be objects and <insert name for faceless object here>.
Yup - that sounds good to me. Indeed, if the syntax is implemented as:How about "refers to"?
Code: Select all
<left: MCExpression> refers to <right: MCChunk>
This would be good also.The other thing I've been wondering is about: "is [not] a <controltype>"... at the moment I check word 1 of the abbrev or long reference so this would avoid a couple of steps there... extracting the word & string comparison.
Code: Select all
if the type of <controlRef> is button then