953c3254e7
core: use canonical import domain of gobot.io for all code
...
Signed-off-by: deadprogram <ron@hybridgroup.com>
2016-12-08 13:24:03 +01:00
95586fa2d0
parrot: move both ARDrone and Bebop under Parrot package
...
Signed-off-by: deadprogram <ron@hybridgroup.com>
2016-12-07 14:22:12 +01:00
4230d2ab2f
examples: remove Master unless needed for less code
...
Signed-off-by: deadprogram <ron@hybridgroup.com>
2016-10-18 21:08:25 +02:00
458c750f33
core: refactor/rename internal name of Master type
...
Signed-off-by: deadprogram <ron@hybridgroup.com>
2016-10-15 20:02:54 +02:00
56558cd9cb
core: Starting refactor of new adaptor/new driver function signatures with ARDrone
...
Signed-off-by: deadprogram <ron@hybridgroup.com>
2016-09-25 11:46:55 +02:00
94d78d777a
core: Refactor tests to allow 'metal' development using Gobot adaptors/drivers.
...
Signed-off-by: deadprogram <ron@hybridgroup.com>
2016-09-12 21:33:14 +02:00
fc82503428
core: Refactor examples to allow 'metal' development using Gobot adaptors/drivers.
...
Signed-off-by: deadprogram <ron@hybridgroup.com>
2016-09-12 21:33:14 +02:00
79fad6bae4
Fixed event race condition
...
If this is anything like the Bebop, then taking off immediately fires the "flying" event, but these events aren't buffered so attaching an event handler afterwards achieves nothing. When I ran the same code for the Bebop (as suggested on the site) it never landed, prompting an emergency connect-with-phone-hammer-buttons scramble. Swapping the event registration with the takeoff method call fixed the problem immediately.
2016-02-17 12:25:14 -08:00
244ec0a0cf
fmt examples
2014-07-10 17:21:21 -07:00
c86123c694
Clean up devices and connections type
2014-07-09 09:38:43 -07:00
7eec236b07
Update examples
2014-07-08 18:36:14 -07:00
7cf1b991a1
Update ardrone examples
2014-06-08 19:50:15 -07:00
d32a5270f2
Update ardrone adaptor, driver and examples
2014-05-20 23:36:44 -07:00
20cbba0789
Update ardrone package
2014-04-28 11:23:12 -07:00
deadprogram