Millisecond Forums

Response latency captured in data file

https://forums.millisecond.com/Topic9997.aspx

By mjeeves - 3/18/2013


Hi,


I’ve created a simple script to capture demographic
information, as shown below. When I extract the data , the file also contains
the response latency. As I don’t need this information is there any easy way to
modify the script so that response latency won’t be recorded?


<dropdown sex>


/ caption = "Sex"


/ options = ("female", "male")


</dropdown>


<textbox age>


/ caption = "Age"


/ mask = positiveinteger


/ range = (18, 110)


</textbox>


<surveypage demographics>


/ caption = "Please answer the following demographic
questions"


/ fontstyle = ("Verdana", -14, true, false, false,
false, 5, 0)


/ questions = [1=sex; 2=age]


</surveypage>


<survey demographics>


/ pages = [1=demographics]


/ responsefontstyle = ("Verdana", -12, false,
false, false, false, 5, 0)


/ itemfontstyle = ("Verdana", -13, false, false,
false, false, 5, 0)


/ itemspacing = 2%


/ showpagenumbers = false


</survey>


 


By Dave - 3/18/2013

Data recording for <survey>s cannot currently be customized. So, no, you cannot prevent latency from being logged to the data file. However, dropping the respective data columns you are not interested in is trivial to do in any data analysis application and can easily be automated.

By mjeeves - 3/18/2013

Okay, thanks for the quick reply.


By mjeeves - 3/18/2013

Dave,


Another issue I am having with this script - when testing this script on the web using Internet Explorer (version 8) the sex question doesn't work properly, I can't select an answer from the drop down box. Any ideas how to address this? The script works fine with Chrome and Mozilla.


Thanks again! 

By Dave - 3/18/2013

when testing this script on the web using Internet Explorer (version 8) the sex question doesn't work properly, I can't select an answer from the drop down box.


This may happen when the ClickOnce launch method is used. Defining a proper /listsize for the <dropdown> should resolve the issue.