<html> <head> <style></style></head> <body class='hmmessage'><div dir='ltr'>I think that you cannot check what sensor is connected..<div>Butia have hotplug and show instantly that a sensor is connect.</div><div>Lego not have that, and the only check possible: get a value, if no gives errors, maybe</div><div>there are a sensor of that type connected..</div><div><br></div><div>><span style="font-size: 12pt; ">The usual approach would be to add a device input to the blocks...</span></div>>device 1, device 2, device 3<div><br></div><div>That can works, but I don't like it taking into consideration that you have put the port</div><div>where each sensor/motor is connected.</div><div><br></div><div>I think in a special block that sets the brick that you want to use.</div><div>For example:</div><div>- you have 2 bricks connected</div><div>-if you want to: read color sensor from brick 1 in port 1</div><div>-turn motor in port b of brcik 2 with power 100</div><div> </div><div>The code will be:</div><div><br></div><div>select brick (1)</div><div>read sensor (color, port 1)</div><div>select brcik (2)</div><div>turn motor (port b, 100)<br><div><br></div><div>See that all the blocks no have changes, only uses the "select brick" to set in the system, which</div><div>brick get the next functions.</div><div>The important of this change: when you have only 1 brick, the code no have changes!</div><div><br></div><div>Opinions?</div><div><br></div><div>Regards!</div><div><br></div><div>Alan</div><div><br><div><div id="SkyDrivePlaceholder"></div><hr id="stopSpelling">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; support-gang@laptop.org<br>Subject: Re: [IAEP] Turtle Blocks question<br><br>Walter,<div>Agreed.</div><div>I am happy to continuing working with you on this.</div><div>Gerald<br><br><div class="ecxgmail_quote">On Fri, Oct 5, 2012 at 2:36 PM, Walter Bender <span dir="ltr"><<a href="mailto:walter.bender@gmail.com">walter.bender@gmail.com</a>></span> wrote:<br> <blockquote class="ecxgmail_quote" style="border-left:1px #ccc solid;padding-left:1ex">On Fri, Oct 5, 2012 at 2:30 PM, Dr. Gerald Ardito<br> <<a href="mailto:gerald.ardito@gmail.com">gerald.ardito@gmail.com</a>> wrote:<br> > Walter,<br> <div class="ecxim"><br> > if we are crossing devices?<br> <br> </div>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> <div class="ecxHOEnZb"><div class="h5"><br> -walter<br> <br> --<br> Walter Bender<br> Sugar Labs<br> <a href="http://www.sugarlabs.org" target="_blank">http://www.sugarlabs.org</a><br> </div></div></blockquote></div><br></div> <br>_______________________________________________ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep</div></div></div> </div></body> </html>