There actually are some real technical limitations with the vscode extension API that prevented them from doing so.
1 Like
We’re working on adding an article to the help.vex.com Knowledge Base to cover all of the keyboard shortcuts in VEXcode, however in the mean time you can press F1 to view the command palette - this will show all available commands + their keyboard shortcuts.
4 Likes
Having a bit of an issue with compiling my converted VCS project. Every time I go to compile, I get several errors saying there are multiple definitions of variables all over the place, until the compiler gives up and spits out an exit code 2. The project runs/compiles just fine when used in VCS. Any help with this?
Also, I must say I’m loving VEXcode so far. Can’t wait to see where you guys go with this, this is a huge upgrade from VCS in every way, as far as I’m concerned.
So after playing around with the editor, here’s my suggestions for changes:
- Remember editor tabs location and visibility after restart
- Solidify saving files. It didn’t save the edits one time.
- Add abs() function (unless it’s fab() which I haven’t tried yet)
- Add option to change font + size.
That’s about it for now, probably would ask for more features that’ll make my life easier 
2 Likes
Vex code looks really nice and professional. Starting with ROBOTC as an example but without 10 years of legacy code really made a difference.
Go to definition for example is one of the features that makes a big difference. It can guide students through learning a lot about programming just because they want to see how provided helper functions work.
Real keyboard shortcuts is great news too.
7 Likes
Linux ver and a .git ext would be great paths to explore
1 Like
I think your gonna need to upload your code? Probably start a new thread. My guess is you are using includes in a funky non standard way.
It’s there - look up the shortcut list F1 - on apple Command Up-arrow and Down-arrow change font size.
I’m only really using #includes pulled in during the import process, and using namespace vex. I could grab a shortened version of the code (I use a lot of comments) later on if you need.
- yes, we will consider doing that.
- ok, should be good but perhaps we still have bugs.
- abs() is available as far as I know.
- Font size is available (as @lacsap explained), we may move to different function keys later.
changing the actual font used we may be able to do, but that’s not something we have looked at yet.
1 Like
you probably have global variable definitions included in every source file. globals must only be declared once, everywhere else you need to reference them you declare them as extern, I will do a separate post on some of these details (which really have nothing to do with VEXcode, it’s normal C/C++ behavior) over the weekend.
1 Like
All my includes are in a vex.h file, as follows:
#include <stdio.h>
#include <stdlib.h>
#include <math.h>
#include <string.h>
#include "v5.h"
#include "v5_vcs.h"
Then in my main cpp file, I only include the h file once.
either start a new thread to discuss this or send me a private message with the code (zip up the project folder using share toolbar button) and I will have a look.
1 Like
As promised, here is the aforementioned VEXcode Knowledge Base article on Keyboard Shortcuts.
3 Likes
There are errors in the shortcuts for Mac - for example Control-c to copy should be Command-C similarly for close window Command-W not Control-W
a proof reader who uses Mac would be helpful.
thanks for getting the list out!
1 Like
Should be fixed now… thanks for pointing that out.
Amusingly enough, we generated the doc and tested each command using the Mac version first, but copy/paste errors happen!
2 Likes
The story of story of my life 
I have just installed the VEX code on my Windows 10 machine and opened the first sample program, “Drive Forward” and compiled it. I received the the following errors.
Go into your project folder and create a new folder called build
3 posts were split to a new topic: VEXcode printf error