Millisecond Forums

Ok, I'll update the version on our desktop computer and then re-post the script on the Inquisit site. Sorry for the confusion regarding the plugin vs. webplayer. The participant downloaded the Inquisit.jnlp, clicked on it and the tasks appeared on the screen. I'm not sure if this constitutes a plugin-induced opening of a web player, but that was the sequence of events. I was incorrect when I stated that it opened a new web browser. After the experiment is completed, then a new tab opens in the web browser, which provides a "thank you" message.

No, using 4.0.7.0 should not create any problems for your script created with 4.0.6.0.

You can always obtain the latest Inquisit Lab version via https://www.millisecond.com/download/ and install it on your system.

> As far as the plugin vs. web player, the participant used the downloaded plugin, which opened up a separate webpage with the
> tasks.

I'm sorry, but I'm not sure what that means. Especially the part about opening "up a separate webpage with the tasks". No launch method will (or at least should) do that (open up a separate webpage). Could you clarify?

Hello,
Your intuition was right. We are using the older version 4.0.6.0. Quick question though. If I update the version for the web script to the current version 4.0.7.0 will this create issues for my program that was created in version 4.0.6.0? When I open my script on my desktop computer I try to update the software version, but I get the error message: "Update check failed, Unable to retrieve update information." Please let me know what I should do. Thanks.

As far as the plugin vs. web player, the participant used the downloaded plugin, which opened up a separate webpage with the tasks.

Thanks for the update. A couple more questions: Which Inquisit Web version are you using? If it's not the latest, please update your launch page to use the latest release (4.0.7.0). Which launch method did the participant in question use? The NPAPI plugin or the Web Player? Perhaps both? Did the issue occur in both or just one? Thanks!

Hello,
I just wanted to provide an update regarding the missing cursor in the VAS task. It turns out the the participant taking the task was indeed using Chrome on a mac. When he used Firefox the cursor reappeared without any issue. Thus, there might be a problem with the VAS code only in mac Chrome. Just fyi. Thanks again for all of your help.

That's 94% of the display width in a pixels (px).

Inquisit Web should (and according to my experience does) play nice with all major browsers, including Chrome. I would rate the likelihood that the mouse issue was due to the browser used as pretty low, though.

As usual, your advice worked perfectly! Quick question. In your modification of the <shape line> size attribute, you specify "0.94px*display.width, 2%" What precisely does the 0.94px indicate?

Finally, as far as the mouse cursor not appearing, do you know which internet browsers are preferred for running inquisit? Perhaps the participant was using a less than desirable browser for the tasks. I know that I have had trouble on my mac running the tasks with chrome, but don't have any trouble using firefox. Thanks.

Observe the difference between:

<expressions>
/ correctionvalue = (display.width - shape.line.width) / 2
/ correctedscore = (trial.mytrial.responsex - expressions.correctionvalue) / shape.line.width * 100
/ roundedvalue = format("%.2f", expressions.correctedscore)
</expressions>

<block myblock>
/ trials = [1-4=mytrial]
</block>

<trial mytrial>
/ stimulusframes = [1=bg, line]
/ inputdevice = mouse
/ validresponse = (line)
/ branch = [trial.showx]
</trial>

<trial showx>
/ stimulusframes = [1=x, debug]
/ trialduration = 2000
</trial>

<shape line>
/ shape = rectangle
/ size = (0.94px*display.width, 2%)
/ position = (50%, 80%)
/ erase = false
</shape>

<text x>
/ items = ("X")
/ txcolor = (red)
/ txbgcolor = (transparent)
/ fontstyle = ("Arial", 10%, true)
/ hposition = 1px*trial.mytrial.responsex
/ vposition = shape.line.vposition
</text>

<text debug>
/ items = ("<%expressions.roundedvalue%>")
</text>

<shape bg>
/ color = (grey)
/ erase = false
/ size = (100%,100%)
</shape>

and

<expressions>
/ correctionvalue = (display.canvaswidth - shape.line.width) / 2
/ correctedscore = (trial.mytrial.responsex - expressions.correctionvalue) / shape.line.width * 100
/ roundedvalue = format("%.2f", expressions.correctedscore)
</expressions>

<block myblock>
/ trials = [1-4=mytrial]
</block>

<trial mytrial>
/ stimulusframes = [1=bg, line]
/ inputdevice = mouse
/ validresponse = (line)
/ branch = [trial.showx]
</trial>

<trial showx>
/ stimulusframes = [1=x, debug]
/ trialduration = 2000
</trial>

<shape line>
/ shape = rectangle
/ size = (0.94px*display.canvaswidth, 2%)
/ position = (50%, 80%)
/ erase = false
</shape>

<text x>
/ items = ("X")
/ txcolor = (red)
/ txbgcolor = (transparent)
/ fontstyle = ("Arial", 10%, true)
/ hposition = 1px*trial.mytrial.responsex
/ vposition = shape.line.vposition
</text>

<text debug>
/ items = ("<%expressions.roundedvalue%>")
</text>

<shape bg>
/ color = (grey)
/ erase = false
/ size = (100%,100%)
</shape>

<defaults>
/ canvasaspectratio = (4,3)
</defaults>

Ok, that is certainly helpful! Knowing that I need to change that setting, how can I ensure that the VAS line and pictures will be displayed similarly on various screen types. Should I specify an aspect ratio at all or just remove that altogether? Thanks.

> One additional clue to the problem might be that when I specify that my VAS line should be 100% of the screen, it takes up maybe 80% of the screen.

That's because you specified

<defaults>
...
/canvasaspectratio = (4,3)
</defaults>

The calculations in the <expressions> are based on display width, not canvas size.

No idea about the mouse issue, I'm afraid.