changeset 257:0a4f6dd227cc

README: Extra troubleshooting info (type 'createProjectSave()' to summon pop-up that saves XML file so far).
Previous commit should read 'scrubber' instead of 'slider'

--- a/README.txt	Wed Jul 01 13:49:01 2015 +0100
+++ b/README.txt	Wed Jul 01 15:19:55 2015 +0100
@@ -67,13 +67,14 @@
 TROUBLESHOOTING
 
 Thanks to feedback from using the interface in experiments by the authors and others, many bugs have been caught and fatal crashes due to the interface (provided it is set up properly by the user) seem to be a thing of the past. 
-However, if things do go wrong or the test needs to be interrupted for whatever reason, all data is not lost. In a normal scenario, the test needs to be completed until the end (the final ‘Submit’), at which point the output XML is stored in ‘saves/‘. If this stage is not reached, a lot of data can be read from the JavaScript Console (see below for how to find it). Specifically:
+However, if things do go wrong or the test needs to be interrupted for whatever reason, all data is not lost. In a normal scenario, the test needs to be completed until the end (the final ‘Submit’), at which point the output XML is stored in ‘saves/‘. If this stage is not reached, open the JavaScript Console (see below for how to find it) and type ‘createProjectSave()’ (without the quotes) and hit enter. This will open a pop-up window with a hyperlink that reads ‘Save File’; click it and an XML file with results until that point should be stored in your download folder. 
+Alternatively, a lot of data can be read from the same console, in which the tool prints a lot of debug information. Specifically:
 	- the randomisation of pages and fragments are logged;
 	- any time a slider is played, its ID and the time stamp (in seconds since the start of the test) are displayed;
 	- any time a slider is dragged and dropped, the location where it is dropped including the time stamp are shown; 
 	- any comments and pre- or post-test questions and their answers are logged as well. 
 
-You can select all this and save into a text file, so that none of this data is lost. 
+You can select all this and save into a text file, so that none of this data is lost. You may to choose to do this even when a test was successful as an extra precaution. 
 
 In Google Chrome, the JavaScript Console can be found in View>Developer>JavaScript Console, or via the keyboard shortcut Cmd + Alt + J (Mac OS X). 
 In Safari, the JavaScript Console can be found in Develop>Show Error Console, or via the keyboard shortcut Cmd + Alt + C (Mac OS X). Note that for the Developer menu to be visible, you have to go to Preferences (Cmd + ,) and enable ‘Show Develop menu in menu bar’ in the ‘Advanced’ tab.