BUG FIX: Cannot uninstall or modify E-Prime using Windows 10 Apps & Features [30307]
BUG FIX: E-Prime 2.0 produces grace period dialog when E-Prime 3.0 license key is attached [24391]
BUG FIX: E-Prime Check for Updates notifications not occurring since an older MFC is not installed [30773]
BUG FIX: E-Prime hangs on the first screen of an experiment run [27780]
BUG FIX: E-Studio Toolbox does not display PackageCall Shortcuts from multiple PackageFiles correctly [27849]
BUG FIX: E-Studio Toolbox does not remove PackageCall Shortcuts when PackageFile is not loaded [26349]
BUG FIX: Experiment Advisor Report cannot open in Google Chrome, Edge (Chromium), or Firefox [30300]
BUG FIX: FFmpeg does not support looping [26068]
BUG FIX: Fully licensed E-Prime 3.0 does not convert Evaluation experiments [39757]
BUG FIX: Initial responses to an Input Mask on Windows 11 not recognized in E-Prime 3.0 [38923]

See more

BUG: OnsetToOnsetTime reports 0 after 25 trials [40215]

Updated August 12, 2022 13:58

This article applies to:

E-Prime 3.0

E-Prime 2.0

Symptoms

OnsetToOnsetTime is reported as 0 after 25 trials when the Object's Duration is set to a new value each trial.

Workaround

Manually calculate OnsetToOnsetTime either in script or post analysis.

c.SetAttrib "TextDisplay1.OnsetToOnsetTimeActual", TextDisplay2.OnsetTime - TextDisplay1.OnsetTime.

See Also:

RELEASE INFO: Known Issues in E-Prime 3.0 [27789]

Comments

0 comments

Please sign in to leave a comment.

Powered by Zendesk