Breaking this out to a different thread to keep organized on tender:
Is the variable attribute full_name used for anything or just ignored? In particular I have historically used it on the variables that are bound to IODevice variables (i.e. the prototypical “juice”) - is it needed here?
Thank you
Mark
Hi Mark,
Is the variable attribute full_name used for anything or just ignored?
Same story as “editable”: Its value is parsed and stored but never used. I don’t know what its original purpose was, assuming it ever had one. While there’s no harm in including it in current experiments, there isn’t any benefit, either.
Chris
Thanks for the explanation of these two attributes.
One suggestion: perhaps you can make MWorks warn when these attributes are found so that they’re not confused with attributes that are used? Having the parser check this would help me.
Thanks for all the recent work. Mark
One suggestion: perhaps you can make MWorks warn when these attributes are found so that they’re not confused with attributes that are used? Having the parser check this would help me.
This is probably a good idea, although it could be very annoying to folks who have existing experiments with many instances of the attributes. Maybe we should add a mechanism for components to mark attributes as deprecated, and then have a global switch to control whether MWorks issues warnings when deprecated attributes are used. I’ll open a ticket.
Chris
I think that proposed solution is great.
Mark