From the ROBOTC blog:
Hi all,
We’ve just released ROBOTC 3.05. Head on over to the download pages to download the latest version!
Change log:
NXT:
- Allow “File Management” window to play multiple sound files and not just a single file.
- Fix bug in implementation of NXT intrinsic function “I2CGetSensorInfo”.
- Holding down gray EXIT button on NXT will now eventually power off the NXT.
- Re-enable support for “sendMessage” on NXT.
- Updated FTC Joystick Driver to include diagnostics and added a critical section around the “no joystick data” fields to prevent false starts.
- “DrawEllipse” was broken for emulator. ‘short’ variable was overflowing; ‘long’ was needed.
- Constant for total number of motors for Tetrix was incorrect (too small). Result is some user defined names for 12V Tetrix motors were not being defined. Applies when Tetrix motor controller was configured on sensor port S3 or S4. Now Fixed.
- Included range checking on game controller joystciks to fit in one byte. Few users reported errors about seeing 2-byte joystick values.
VEX:
- New Automatic Firmware Updater for VEX Cortex – Choose one menu option and ROBOTC takes care of the rest (putting into bootload/downloading both master and ROBOTC firmware)
- Updated installer to automatically install the VEX Cortex drivers and Prolific USB-to-Serial Drivers upon install.
- Updates to the RVW Natural Language files to include remote control and microcontroller button commands.
- New standard model files for PLTW Testbeds
- By default “Com Port lists” will not include all serial ports. They will only the ports that match the current platform/use selection. A registry preference (“Advanced Environment” tab) can be used to restore to the current (3.04 release) of including all ports.
- Updated Error Messages for Firmware/Program downloads.
- New Sample Programs for 4-motor joystick control.
- Added new variable “bStopTasksBetweenModes” to allow VEX users to disable the allTasksStop function from running between autonomous and teleop modes
General/Other:
- Compiler was not generating error when “typedef” variable was used in an expression. Fixed.
- ADD “__NAME__” to preprocessor predefined variables.
- Fix code generation bug for “const string” array variables. Compiler would incorrectly use empty string instead of reference to array variable in constant pool.
- Rightmost character of block of italic formatted source file had “slant” clipped by the background of the next block of text. Fixed.
- Expand opcodes for “shift left/right” to support ‘long’ variable as shift size amount.
- Fix definition of “degreesToRadians” intrinsic. It was not working when the parameter was a numeric constant
So we can use Bluetooth more like the old way now? Not that I don’t like the new way but the sendMessage one just seems easier & there’s more info about it online.
Seems that way. I haven’t tested it yet, I don’t have my NXTs with me right now.