evaluation of unset timers -- change across MWorks versions?

Benedict's Avatar

Benedict

22 Jul, 2019 07:44 AM

Hi,
I saw in a previous discussion that when evaluating whether an unset timer has expired, this always results in "true" (which matches my experience). I was wondering if this used to be different in previous versions of MWorks. I'm currently adapting an old experiment (that was written in MWorks 0.5 or 0.6) from our lab which tries to evaluate an unset timer. As expected, it evaluates it as true, but that's not what it is actually supposed to do. So I was wondering whether this was different when the experiment was first programmed.
Thanks
Benedict

  1. Support Staff 1 Posted by Christopher Sta... on 22 Jul, 2019 02:01 PM

    Christopher Stawarz's Avatar

    Hi Benedict,

    I saw in a previous discussion that when evaluating whether an unset timer has expired, this always results in "true" (which matches my experience). I was wondering if this used to be different in previous versions of MWorks.

    As far as I can tell, this was how timers behaved in MWorks 0.5, too.

    Cheers,
    Chris

  2. Christopher Stawarz closed this discussion on 24 Jul, 2019 01:53 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac