This article applies to:
By using attribute references "[...]" that reference attributes on a List, you can eliminate the number of unique E-Objects in an experiment and easily modify your paradigms. This reduces the need for multiple objects that may contain the same script or stimuli.
For example, a List containing an attribute named "theImage" can be made. This attribute can have the information for different images specified (i.e., Image1.png, Image2.png, etc.). Instead of creating multiple Slides or ImageDisplays that show all the images, one E-Object can be created that has a reference (i.e., [theImage]) back to the attribute.
While the main benefit is an easily modifiable paradigm and a smaller size for your experiment file, there are actual errors that stem from overly bulky and redundant designs. These often occur while loading external resource files, especially when the files are relatively large in size. E-Prime allocates a set amount of memory for each E-Object at Runtime. Therefore, these errors can occur on machines with a relatively large amount of memory when sourcing in large external files.
The error messages that accompany these types of issues are often generic and do not tell you exactly what the fix is. For example, a common error to receive for this issue is "Internal error has occurred. Marker: 2006."
When you use more attribute references to present external resource files, you typically reduce the amount of time it takes to load your E-Objects at Runtime, use less hardware resources, and reduce the likelihood of these errors.