I recently got a new laptop and had to download vex v5 code again and I downloaded the block one on accident because the other one said “Pro” instead of text like the old one. I downloaded the Pro one and it was fine until I opened the code and everywhere it said “vex” was an error, and in all of the programs. Another member of the team still had the vex v5 text version and all the programs were working perfectly fine. We tried importing the programs back into the new software to try and see if it would change them to work with this version but for some reason it wouldn’t do anything if we clicked the import button so something must have been off. Has anyone else had similar problems and can help???
Interesting. I have never heard of such an error.
Have you tried building the project(s)? The linter (the thing that’s giving you the errors) needs information from the compiler (for stuff like include paths), and it might not have that yet.
1 Like
Thank you for the help, but we figured it out. We have our programs in one big shared google drive and my other teammates and I can all edit the programs and it updates on the other computers as well. For some reason when they are backed up in google drive it gives us those errors and when they aren’t it works fine.
google drive (or I should really say google docs) can cause issues when it changes simple quote characters to curly quote characters.
C compilers do not like curly quotes.
or
it may be an issue with path names, VEXcode can have issues with network drives.
6 Likes