If an object uses an [attribute] reference for its Filename property and the resolved value cannot be found on disk, this module is detected during compile.
Run-time errors can be prevented when the Experiment Advisor resolves the attribute references and searches for the resolved filename during script generation. An example of this warning is shown below. The Experiment Advisor warning identifies the following information:
- the object with the problematic attribute reference ("The 'Stimulus' object...")
- the object property that is assigned to an attribute reference ("…its Filename property")
- the name of the attribute reference ("Attribute: [Stimulus]")
- the resolved value of the attribute reference that cannot be loc/ated ("Resolved: SilverCar.bmp")
This topic applies to:
E-Prime 2.0 Professional
This topic introduced in E-Prime 220.127.116.11 or later
12/14/2012 9:51:00 PM
|I just tried this with a simple test -- Added an ImageDisplay, entered a Filename of [Session].bmp with no corresponding image files on disk, compiled & ran it, and got the usual "Unable to load image file" runtime error, with no warnings from Experiment Advisor. What am I missing? Thanks.|
12/14/2012 10:18:00 PM
|The check is exclusive to checking those filename properties against List values and cannot detect complex attribute names like [folder][file].bmp or attributes created outside of a List (c.SetAttrib, StartupInfo, etc).|
To provide an instance of this working, prior to open the SlideRT experiment, rename up.bmp to foo.bmp and then generate the experiment, the finding will occur.