You can safely ignore the vi tester folder. It was my attempting at using unit testing for the scripting functions, but it was too cumbersome dealing with all the different app instances. If you can figureout a way to make 8it work, please go ahead. I just invested way too much time and realized it was going nowhere. Maybe someone else will have better luck.
Manual testing:
There is a folder called "code for testing" in the 1-cleanup branch. Once that gets merged in, it has a project with a simple actor that uses all 3 types of messages, so you can run the scripting on that and look at the results as a quick sanity check. It's not a very thorough test, but its the best I came up with.
\ No newline at end of file
There is a folder called "code for testing" in the 1-cleanup branch. Once that gets merged in, it has a project with a simple actor that uses all 3 types of messages, so you can run the scripting on that and look at the results as a quick sanity check. It's not a very thorough test, but its the best I came up with.
Contribution Guidelines:
For now, just wait until I finish the cleanup branch and merge it back into master. It will save you a lot of headache.
After that, just simply fork it, make your changes and submit a merge request into master.
