In dash studio, the only one of those I can see is property "testing"
DashStudio only shows and uses Properties, same for Available Properties.
This is because properties contain values, that you can then display verbatum, or within a formula to determine if something should be shown or where.
Events are triggers, that can be matched to Actions.
DashStudio has Actions, such as NextScreen, which makes the dashboard go to the next dashboard page, while SimHubs DataCor ships with NewLap, Flag_Yellow, etc.
EasyScripts Events are Events (duh), but Logging is an Action.
To map Events to Actions go to "Controls and events" (Keyboard icon) and go into the Events tab. There create a new binding for Source test and Target test1. You can also use this screen to try if your logging function works and logs to the correct place by pressing "Trigger Action Now".
Now, come to think of it, with your application of logging car performance data through the logging action we might have a problem with file access.
Short version: When the Event triggers SimHub forwards the function call to the logging action, which goes and launches itself async. The async function then runs the script, and takes the output and calls System.IO.File.AppendAllText(file, text); to write the data into the file. How precisely it works is unknown, it will however likely open (or try to open) a handle on the file, then write the data into the file and then close the handle.
Now, the issue is with async is that we don't know if the previous operation has finished, and you can't open a filehandle when one is already open, which would throw an exception.
We can check by going in SimHub to logging (if you don't see it make sure to select "Show logging tab" within SimHub Setting, General tab, General Section).
If you see the error "EasyScript: Exception thrown when trying to log to file", then your trigger rate should be decreased, and I maybe should look into doing something about this.
I am probably overthinking this, again
