embedding scriptingrt in qualtrics in chrome

In earlier posts and the manual we described how to embed scriptingrt files in qualtrics.

There is now a problem with this. Qualtrics serves its pages using secure http, or https. However, when you put your own flash files and the swfobject javascript library on your server, these servers will usually be regular http. Until recently, that was not a problem, but as of recently, Chrome bulks at this combination: When it displays a http website, it will not include anymore “unsafe”, regular http content. You recognize this when the small silver shield appears in the address bar. Or you can open the developer console, where you see the error message.

As a result, your flash file is not shown in Chrome. At the moment, Firefox and IE will still show it, but that might go away soon as well.

The solution is to serve your content from a secure http server as well.

Unfortunately, it is not cheap. My service provider charges over 70 € per year for a registered SSL certificate, and nothing else will do. However, there is a workaround: You can put your files in a your dropbox. Both links in the “public” dropbox folder and “share links” seem to come from https by default.

I quickly tested this last week, it seems to work. Also, it seems to work that these dropbox-served flash files then send their data to a php script on a regular (non https) server.

If that doesn’t work for you, please comment below.

In principle, though, dropbox-served files will probably load more slowly. So it might be a good idea to either get access to your institution’s https server, or to upgrade your own.

UPDATE 11/10/2013: it seems that is not a problem anymore? At least in a first test today, it was possible again to include non-https-served flash files in qualtrics.

problem with setting some attributes by scripts in ScriptingRT

When we write ScriptingRT experiments with between participant manipulations, we want to put as much as possible in scripts, so that we don’t have to create separate versions.

This works well with some attributes. For instance, you can change the contents of a text of a <Text/> at runtime:

After defining the item,

<Item id="p1" type="-"> 
    <mx:Text id="p1upt" verticalCenter="+150" horizontalCenter="0" text="?"/> 
  private function initVars():void {
    p1upt.text = "kite";

This also works for attributes like instruction of an <Instruction/>

However, it does not work when I try to change the attributes positive and negative of a <Testpart/>. I am not sure why this doesn’t work, presumably because this is used to build the item data structure before the item is evaluated at runtime.


restriction of scriptingRT

We checked whether scriptingRT can be used to run studies that want to distinguish between more than 2 answers with a keyboard. Unfortunately, that is not the case. So, you can program a Stroop task where people have to distinguish between two colors, and press one of two keys. However, you cannot program a Stroop task where people have to distinguish between four colors, and press one of four keys. More precisely, you can, but the protocol cannot list the actual responses, only whether the answer was positive or negative, which are only two categories.

This comes out of our starting point, DMDX, where the behavior is the similar.

We can certainly change this at some point, and allow saving the actual response in the protocol, but it depends on having programming ressources to do so. For the time being, this is a restriction.