Millisecond Forums » Millisecond Forums » Inquisit 5 » Self-Paced Reading Task error

Self-Paced Reading Task error

luca7 — Wed, 26 Dec 2018 08:35:30 GMT

Hello,
I'm back on a self-paced reading task that I run last year and it emerged a new issue.
As illustrated in the picture below, the script incorrectly adds dashes to the end of the sentence. The extra dashes appear once the end of the sentence is reached.
This error can be replicated both offline (downloading the script here https://www.millisecond.com/download/library/selfpacedreading/ and running it using the latest version of Inquisit lab 5) or online clicking "run test online" at the same web address.

Hope there is an easy solution!
Thank you for your help.
Luca

RE: Self-Paced Reading Task error

luca7 — Wed, 26 Dec 2018 08:35:30 GMT

I'll do that. Thank you very much again for your help!
Luca

RE: Self-Paced Reading Task error

Dave — Wed, 26 Dec 2018 08:29:49 GMT

[quote]

[b]luca7 - Wednesday, December 26, 2018[/b]

thank you very much!
Could you please indicate what you changed, so I can modify my version of the task?

Luca

[/quote]

In your script's <expressions> element, replace the existing /getpostwindow expression with

/ getpostwindow = if(abs(length(values.inputstring-values.winend))!=0) {values.postwindowstring = substring(values.maskstring,
values.winend, abs(length(values.inputstring)-values.winend))} else values.postwindowstring = "";

and replace the existing /getpostwindowhl expression with

/ getpostwindowhl = if(abs(length(values.inputstring-values.winend))!=0) {values.postwindowstringhl = substring(values.maskstringhl,
values.winend, abs(length(values.inputstring)-values.winend))} else values.postwindowstringhl = "";

RE: Self-Paced Reading Task error

luca7 — Wed, 26 Dec 2018 08:21:56 GMT

thank you very much!
Could you please indicate what you changed, so I can modify my version of the task?

Luca

RE: Self-Paced Reading Task error

Dave — Wed, 26 Dec 2018 08:15:33 GMT

[quote]

[b]luca7 - Tuesday, December 25, 2018[/b]

[/quote]

Thanks for pointing out the issue. Fixed in the attached revision.