NEW FEATURE: ResetLoggingProperties reset their logging properties at begin of each Procedure run [17763]

Follow

Comments

2 comments

  • Avatar
    David McFarlane

    This article states, "E-Prime 2.0 introduces the ability to allow objects to reset all of their logging properties at the begin of each procedure run."  This seems inaccurate to me.  It should read, "E-Prime 2.0 forces objects to reset all of their logging properties at the begin of each procedure run."  I.e., EP2 does not introduce the ability to allow this behavior, because it does not allow the user to disable this behavior.  Or am I missing something?

    Indeed, typically I would prefer this behavior.  But I have a program where I actually want the next run of the Procedure to show the response from the previous run of the Procedure, but this new behavior makes that hard.  Of course, I could overcome this new behavior by introducing more global variables and code to preserve the logging properties between runs of a Procedure, but this seems like an ugly kludge, especially since the logging properties are already global and earlier versions of EP did this without any kludge.  Is there some way that I can selectively revert to the previous behavior to suit my purposes?

  • Avatar
    David McFarlane

    Figured this out myself later the same day -- Just go to the Logging tab on the Properties Pages of the stimulus object, find the "Reset logging properties to zero/default at the start of each Procedure run" checkbox below the Property Logging list, and uncheck it.  Obvious in retrospect, not so obvious from the documentation

Please sign in to leave a comment.

Powered by Zendesk