VEXcode V5 Text Version 1.0.1 Release

VEX News
#1

As promised earlier, we are happy to release VEXcode V5 Text Version 1.0.1. It can be downloaded here:

New Features in 1.0.1:

  • Added “Expert Robot Configuration” toggle to project settings to disable the Graphical Robot Configuration tool.
  • Resolved an issue with opening Example Projects after importing a .VEX file.
  • Added two missing commands to Drivetrain Autocomplete list.

And for reference, expand below to see the features from the 1.0.0 release.

1.0.0 Features

New features in 1.0.0:

  • Improved code readability by updating the V5 SDK version to use global enums (no :: needed by default) and add default parameters to commands that accepts different unit types.
    • Before: LeftMotor.spin(vex::directionType::fwd);
    • After: LeftMotor.spin(forward);
  • Added 50+ new example projects.
  • Added 8 new tutorial videos.
  • Added “Tools” menu in the toolbar, including commenting tools, font size adjustment, code formatting tools, and access to advanced API documentation.
  • Added Find / Replace features to the “Edit” menu.
  • Implemented “Command Help” feature. Accessible from the “Command Help” option in the right-click context menu after positioning the cursor on a command.
  • Implemented “Command Reference” feature listing primary API commands via the help panel. Command reference will display commands based on the configured devices in the project. Each command reference command has a simple “copy command” button.
  • Implemented Graphical Robot Configuration. Accessible by the Robot Configuration button in the toolbar.
  • Implemented a User Feedback feature for users to send feedback in the application.
  • Added Simplified Autocomplete for VEX API commands to limit complexity for new users. More advanced users can use the “Enable Expert Autocomplete” project setting in the project details window to expose all API commands.
  • Added wait() and waitUntil() macros to match VEXcode V5 Blocks.
  • Implemented Light Editor Theme preview feature. To view, change the theme option in from File -> Preferences.
  • Added a “Project Update” feature to migrate VEXcode V5 Text 0.9 and earlier projects to VEXcode V5 Text 1.0.

Technical details of new features:

  • Robot Configuration: Devices that are added to the Robot Configuration panel will auto-generate code snippets required to use the device. These devices will be initialized with the “vexcodeInit()” command.
  • Robot Configuration: Device declarations will populate the robot-config.h file - which is a read-only file.
  • Project Update: When the user opens projects created prior to VEXcode Text v1.0, the user will be provided an option to “Update Now”, “Update Later”, or “Don’t Ask Me Again”.
  • Project Update: Imported VCS VEX C++ and VEX C++ Pro projects will not support the Robot Configuration or the new Simplified Autocomplete features to avoid conflicts with backwards compatibility.

A few known issues with this release:

  • Simplified version of Autocomplete will be continuously improved for the future releases.
  • Accelerometer is not showing up in Autocomplete
  • “Editor Font Zoom Reset” under “Tool” menu on Windows, resets to slightly smaller font than the default

As always, we appreciate any user feedback. If you come across something that doesn’t seem right, please let us know below or by using the Feedback tool inside of VEXcode V5 Text!

20 Likes
#2
#3

Any way to set up a 4 motor drivetrain with the “Expert Robot Configuration”?

1 Like
#4

This should work… haven’t had a chance to test. I used the Graphical Robot Config to create the base, switched to expert mode, then added the motor groups and updated my Drivetrain constructor.

// VEXcode device constructors
motor LeftDriveSmart = motor(PORT1, ratio18_1, false);
motor LeftDriveSmart2 = motor(PORT8, ratio18_1, false);
motor RightDriveSmart = motor(PORT9, ratio18_1, true);
motor RightDriveSmart2 = motor(PORT10, ratio18_1, true);
motor_group LeftSide = motor_group(LeftDriveSmart, LeftDriveSmart2);
motor_group RightSide = motor_group(RightDriveSmart, RightDriveSmart2);
drivetrain Drivetrain = drivetrain(LeftSide, RightSide, 319.19, 295, 130, mm, 1);
4 Likes
Issues with motor_group
Issues With Motor Groups
#5

By the way, 4-Motor Drivetrains is slated for a future update for both Blocks and Text.

9 Likes
#6

Thank you, works perfect!

2 Likes
#7

This did not work for me on robot c

2 Likes
#8

Vexcode is an entirely different coding software. It uses c++, robotc does not.

1 Like
#9

Pooh ok thanks man cause I was wandering how this would work on a cortex instead of a v5 brain. Sadly since my team is from South Africa we can’t afford the v5 stuff. Should we buy it

2 Likes
#10

For the competitions It’s almost a requirement, but for anything less than that the cortex is more than sufficient.

1 Like
#11

Ok thanks for the much appreciated advice that I so very much wanted

2 Likes
#12

is there a way to configure the camera on expert config mode? I don’t want to make 2 include files just for the camera configurations. Thanks!

1 Like
#13

This version of vexcode is running in the background and using a lot of battery, is there any way to turn this off? Is anyone else having this issue?

1 Like
#14

Is there any way to do a two stick drive with a drivetrain?

1 Like
#15

You mean tank drive?

1 Like
#16

Yes, I mean as a tank drive. If you configure it with the graphical configurer, it adds a ton of really confusing code, is there an easy way to do it?

1 Like
#17

Idk what it looks like with blocks, but in text it looks like this
Lw1.spin(controller1.axis3.value);

1 Like
#18

Question #1:

Can you share a link to these tutorials?

Question #2:
Is the drivetrain function (which looks awesome) limited to a tank drive or can it also be used for x-drives or mechanum wheels?

3 Likes
#19

How does one go about enabling this “Expert Robot Configuration,” I’ve been looking and haven’t been able to find out how.

1 Like
#20

see this.

5 Likes