I have a good sized .chip file that is a work-in-progress that I can get to SEND TO successfully and run (or at least appears to, hunting down a logic error in the code), but when I SAVE TO, VetusGUI returns that it completed the save successfully way to soon. First I was thinking Vetus hardware was being efficient and saving the SEND TO version since there were no changes... However, the test does not show in the menu on the hardware.
When I REFRESH to pull the current list, there is a blank file at the bottom of the list in VetusGUI. If I load that from the hardware into VetusGUI, I will get either the correct Code, Chip Name, Num Pins, Chip Type, and Image fields but the String# fields will all be empty or have invalid characters in them - OR - I will get nothing.
A full reboot of the hardware, close/open of VetusGUI and doing a direct SAVE TO results in the same type of behavior.
I'm on Windows 11, I have updated the hardware to 1.0.3. I have other much smaller test chip files that saved and run without issue.
It's not allowing me to attach the .chip file even if I rename as .txt. It's 380 lines so didn't want to wall-of-text the post.
it could be that. Right now each test is limited to 255 lines of code. I don't know what all is happening or if you have problems with others but that could be the issue. If you can, use classes for repeatable stuff for now. I am thinking about doubling the code size but I'm not sure yet. In any case, that's the limit right now. I have to get the docs updated and fix some mistakes and add new stuff I just haven't had time yet. I'm working on it.
If you haven't seen the updates for using functions you can go to the downloads page and see previous updates and what was in it. functions are explained there. It'll be in the docs soon.