Kevin Andersen ecbbacd4c0 It seems like there's a tradeoff between how we choose to set the max power of the motors. Previously, I had set the motors' max power (torque) to follow their target speed, meaning they accelerated smoothly, but also lost their torque. Then in the following commit I changed the max power to 100 which means maximum torque to achieve the target speed, which resulted in very abrupt accelerations and erratic motor movement when changing speeds: ... 873b56c985 In the following commit I changed the functionality so that we add a fixed amount (10) more power than the target speed, e.g. for speed 50 it would provide power 60. This is fine for high speeds, but for low speeds it provides poor torque: e3cdbffa2a I assume it would be possible to design some sort of calculation that enabled high torque for low speeds, and vice versa. I will discuss with the team.		2019-04-08 17:56:54 -04:00
..
base64-util.js	Adding Ev3 extension with three test blocks to latest device-connection work, auto-connecting to device for now.	2018-07-09 13:49:40 -04:00
cast.js	Satisfy linter	2018-11-29 14:07:27 -05:00
clone.js	Use ES6 style classes	2017-04-17 19:42:48 -04:00
color.js	Use ES6 style classes	2017-04-17 19:42:48 -04:00
get-monitor-id.js	Normalize capitalization of sensing_current block fields during sb2 import and during monitor id generation. Update monitors integration test to include sensing_current block monitors.	2018-11-08 14:11:30 -05:00
jsonrpc-web-socket.js	remove logging	2018-07-09 13:49:41 -04:00
jsonrpc.js	Adding check for open request before calling reject/resolve. Resolves #1764.	2018-11-27 09:43:53 -05:00
log.js	Pass with --fix	2017-04-17 15:10:04 -04:00
math-util.js	It seems like there's a tradeoff between how we choose to set the max power of the motors. Previously, I had set the motors' max power (torque) to follow their target speed, meaning they accelerated smoothly, but also lost their torque. Then in the following commit I changed the max power to 100 which means maximum torque to achieve the target speed, which resulted in very abrupt accelerations and erratic motor movement when changing speeds:	2019-04-08 17:56:54 -04:00
maybe-format-message.js	Add tests for converting extension metadata	2018-04-09 15:37:08 -07:00
new-block-ids.js	Add a utility for giving blocks new IDs, use it for sharing blocks.	2019-02-06 10:16:22 -05:00
rateLimiter.js	Rate-limiting with a token bucket for the WeDo extension (#1540)	2018-08-29 17:37:59 -04:00
string-util.js	Fix issue where non-strings were getting passed in to escape functions for handling special characters that can appear in xml. Add tests.	2019-02-07 11:58:10 -05:00
task-queue.js	Fix TaskQueue constructor when no options passed	2019-02-15 15:20:38 -08:00
timer.js	Add clearTimeout to Timer and MockTimer	2019-02-11 12:14:44 -08:00
uid.js	Pass with --fix	2017-04-17 15:10:04 -04:00
variable-util.js	Fix loading broadcast messages with special characters for projects that were converted from 2.0.	2019-02-06 16:58:46 -05:00
xml-escape.js	Fix issue where non-strings were getting passed in to escape functions for handling special characters that can appear in xml. Add tests.	2019-02-07 11:58:10 -05:00