Does anyone know how the "save timings" is implemented?
Specifically, is it client-side or server-side, ie. is it sensitive to lag and transit time from a client to server?
Or measured client side so the recorded time is not sensitive to lag?
My solution for IATs has been to use array-text questions with JavaScript to present the terms and record the results. As this is all client-side, there is no noticeable lag.
Here's a screenshot of the concept (the results array would, of course, be hidden in a live survey):
Cheers,
Tony Partner Solutions, code and workarounds presented in these forums are given without any warranty, implied or otherwise.
Think timing is set in PHP, but not sure.
(have a js timing, but validate in PHP)
Assistance on LimeSurvey forum and LimeSurvey core development are on my free time.
I'm not a LimeSurvey GmbH member. -
Professional support
-
Plugins, theme and development
. I don't answer to private message.
The following user(s) said Thank You: sterlingbates
Thanks, I am not sure that information is detailed enough.
In the case of timings measured at the 100th to 1000th of a second, then knowing when the timing starts and when it stops is critical.
Case 1: php timing. Timing starts from when the server sends the page, and then stops when the response is received by the server. This does NOT work for IAT style assessments
Case 2: js timing. Timing starts from when the page is displayed to the user and stops from the moment the person clicks the answer.
While for most survey situations, the difference between Case 1 and 2 is negligible. However, for IAT style testing, the differences are significant.