<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><span style="font-size: 12pt; ">> Date: Sat, 6 Oct 2012 14:18:10 -0400</span><br><div>> Subject: Re: [IAEP] Turtle Blocks question<br>> From: walter.bender@gmail.com<br>> To: gerald.ardito@gmail.com<br>> CC: alanjas@hotmail.com; iaep@lists.sugarlabs.org; support-gang@laptop.org; davidson.iain@gmail.com; forster@ozonline.com.au<br>> <br>> On Sat, Oct 6, 2012 at 2:08 PM, Dr. Gerald Ardito<br>> <gerald.ardito@gmail.com> wrote:<br>> > Walter,<br>> ><br>> > I have been testing it out this afternoon. It works really well.<br>> > I only have one We Do here, so I can't test out if it sees different<br>> > devices.<br>> ><br>> > There is one quirky thing. When the script is running a motor, the Stop icon<br>> > disappears. Then, if you use ctrl-s to stop the script, the blocks<br>> > disappear.<br>> <br>> You could just keep a motor=0 block around... I suppose I could<br>> auto-stop the motor when the program stops executing, but I think that<br>> might limit the utility somewhat. (The Stop Button is for the Turtle<br>> Art program, not the WeDo motor.)</div><div><br></div><div>In the Nxt Plugin (and the Butia) I add the "stop motors" in the stop of the Turtle.</div><div>When the robot is "crazy" and you want to stop it, the best way (beyond turn off) is</div><div>click on the stop button off the Turtle.</div><div><br></div><div>The WeDo plugin have the "stop motors" function: when you click on the "stop"</div><div>of the turtle, the WeDo motor is stopped??</div><div><br><br>> > And a question, how do you reverse the direction of the motor?<br>> <br>> Should reverse with a negative number.<br>> <br>> enjoy.<br>> <br>> -walter<br>> <br>> > Thanks.<br>> > Gerald<br>> ><br>> ><br>> > On Sat, Oct 6, 2012 at 11:46 AM, Walter Bender <walter.bender@gmail.com><br>> > wrote:<br>> >><br>> >> On Sat, Oct 6, 2012 at 1:27 AM, Alan Jhonn Aguiar Schwyn<br>> >> <alanjas@hotmail.com> wrote:<br>> >> > I think that you cannot check what sensor is connected..<br>> >> > Butia have hotplug and show instantly that a sensor is connect.<br>> >> > Lego not have that, and the only check possible: get a value, if no<br>> >> > gives<br>> >> > errors, maybe<br>> >> > there are a sensor of that type connected..<br>> >> ><br>> >> >>The usual approach would be to add a device input to the blocks...<br>> >> >>device 1, device 2, device 3<br>> >> ><br>> >> > That can works, but I don't like it taking into consideration that you<br>> >> > have<br>> >> > put the port<br>> >> > where each sensor/motor is connected.<br>> >> ><br>> >> > I think in a special block that sets the brick that you want to use.<br>> >> > For example:<br>> >> > - you have 2 bricks connected<br>> >> > -if you want to: read color sensor from brick 1 in port 1<br>> >> > -turn motor in port b of brcik 2 with power 100<br>> >> ><br>> >> > The code will be:<br>> >> ><br>> >> > select brick (1)<br>> >> > read sensor (color, port 1)<br>> >> > select brcik (2)<br>> >> > turn motor (port b, 100)<br>> >> ><br>> >> > See that all the blocks no have changes, only uses the "select brick" to<br>> >> > set<br>> >> > in the system, which<br>> >> > brick get the next functions.<br>> >> > The important of this change: when you have only 1 brick, the code no<br>> >> > have<br>> >> > changes!<br>> >> ><br>> >> > Opinions?<br>> >> ><br>> >> > Regards!<br>> >> ><br>> >> > Alan<br>> >> ><br>> >> > ________________________________<br>> >> > From: gerald.ardito@gmail.com<br>> >> > Date: Fri, 5 Oct 2012 14:45:48 -0400<br>> >> > To: walter.bender@gmail.com<br>> >> > CC: alanjas@hotmail.com; iaep@lists.sugarlabs.org;<br>> >> > support-gang@laptop.org<br>> >> ><br>> >> > Subject: Re: [IAEP] Turtle Blocks question<br>> >> ><br>> >> > Walter,<br>> >> > Agreed.<br>> >> > I am happy to continuing working with you on this.<br>> >> > Gerald<br>> >> ><br>> >> > On Fri, Oct 5, 2012 at 2:36 PM, Walter Bender <walter.bender@gmail.com><br>> >> > wrote:<br>> >> ><br>> >> > On Fri, Oct 5, 2012 at 2:30 PM, Dr. Gerald Ardito<br>> >> > <gerald.ardito@gmail.com> wrote:<br>> >> >> Walter,<br>> >> ><br>> >> >> if we are crossing devices?<br>> >> ><br>> >> > Egon Spengler: Don't cross the streams.<br>> >> ><br>> >> > The usual approach would be to add a device input to the blocks...<br>> >> > device 1, device 2, device 3... But also, I should do a better job of<br>> >> > autodetecting which sensors are available. The whole thing should be<br>> >> > more dynamic.<br>> >> ><br>> >> > -walter<br>> >> ><br>> >> > --<br>> >> > Walter Bender<br>> >> > Sugar Labs<br>> >> > http://www.sugarlabs.org<br>> >> ><br>> >> ><br>> >> ><br>> >> > _______________________________________________ IAEP -- It's An<br>> >> > Education<br>> >> > Project (not a laptop project!) IAEP@lists.sugarlabs.org<br>> >> > http://lists.sugarlabs.org/listinfo/iaep<br>> >><br>> >> Attached is a BETA version of a new WeDo plugin that supports multiple<br>> >> devices. It follows a schema similar to what Alan proposes above. I<br>> >> only have one device, so it is not tested for multiple devices,<br>> >> however, it seems to work for one device and includes a new feature<br>> >> which tests for devices before each start, rather than just at launch,<br>> >> so devices and be plugged in and unplugged without having to restart<br>> >> Turtle Art.<br>> >><br>> >> Feedback greatly appreciated.<br>> >><br>> >> regards.<br>> >><br>> >> -walter<br>> >><br>> >> --<br>> >> Walter Bender<br>> >> Sugar Labs<br>> >> http://www.sugarlabs.org<br>> ><br>> ><br>> <br>> <br>> <br>> -- <br>> Walter Bender<br>> Sugar Labs<br>> http://www.sugarlabs.org<br></div> </div></body>
</html>