Hi Maarten,
I will send you the link for the beta-installer directly. The Clip Logger is a tool within the Widget Designer, thus it runs on XP without problems.
Yes, I would define a variable for each button / each script you want to count.
For example, first you run the scripts
VInt,Count_Media1,0
VInt,Count_Media2,0
...
VInt,Count_Fader1,0
...
Now, if you go to the Variable list, you see these variables written down. You only have to declare variables once per project. If you save the file, the variables and their current values are saved.
Then, for example you create a CS button, where you program the scripts depending how you want to control the the timeline in Pandoras Box (with active values for the Mediachange: DeviceSetMedia,'SiteID','DeviceID','FolderID','FileID' or with jumping to specific Cues: SeqGotoCue,'SeqID','CueID' and SeqSetState,'SeqID',Play. Afterwards you type in the script VAdd,'VarName','Var1','Var2' e.g. VAdd,Count_Media1,Count_Media1,1 that will add 1 to the current value of the variable. So that is why you could declare a variable for everything, and it does not matter whether you program it on the on-click or toggle or mouse enter or on page change or or or.
I am not sure, what you mean with "And where do you read out the clicks? Is it a file made with the input/output node system?" Maybe the more detailed description above has already solved it? The click on the button executes the script to change the media and afterwards the script to increase a variable.
At the end of the day it could make sense to write down the value of each variable (or you program something with excel output nodes and making a statistics diagramm out of it
and run the scripts to reset the declared variables to zero
VValue,Count_Media1,0
I hope I explained it understandingly