Re: Problems with sensor testing in 1.40 public RC1
Responding to another item in the thread.
Whether you use numeric index, or enum, or user assigned name for motor is a matter of personal preference.
The vast majority of end user feedback was that "motorA" was preferred over "0". And it does correspond to the A, B, C naming convention adopted by LEGO.
My personal preference is a user defined descriptive name;
ROBOTC has been recently enhanced to support the HiTechnci "accessory" motor controllers that connect to sensor ports and provide control over two new 12V motors. This is part of the kit for the new FIRST FTC robots. Up to four motor controllers (or hubs) can be daisy chained to each sensor port.
I agree that a enun like "motor_S1_C3_1" to indicate the first motor on the third controller connected to sensor port is a little confusing. But it is a heck of a lot less confusing than knowing this is motor index "8". Of course this is why I personally prefer the user defined name approach described in the above code example.