|
|
 | | Re: NXT-G print to text?
|
| (...) Nice defense! I'm sure the NI engineers have anticipated the complexities you've mentioned. Hence, no scary print-to-text. However, I'm not asking for anything so ambitious. I hold that a print-to-text within the context of plain NXT-G (no (...) (18 years ago, 21-Jul-08, to lugnet.events.brickworld, lugnet.robotics)
| | | | | Re: Worm gear... whence the length?
|
| "Brian Davis" <brdavis@iusb.edu> wrote in message news:K49Az5.87G@lugnet.com... (...) The problems with the worm gear that you describe are due to the fact that it has to fit into this part in this set and others, which was designed to accomodate (...) (18 years ago, 20-Jul-08, to lugnet.events.brickworld, lugnet.robotics)
| | | | | Re: Worm gear... whence the length?
|
| (...) The number of thread has to be an integer. If not, you could not been able to use multiple worm gear on a same axle. And the thread pitch is determined from the straight gears pitch. (which is something like nPi/m studs (n,m being intergers). (...) (18 years ago, 19-Jul-08, to lugnet.events.brickworld, lugnet.robotics)
| | | | | Re: NXT-G print to text?
|
| (...) Obviously, NI is so confident they've reached their design goal: that every 9 year old should be able to program in NXT-G without calling tech support. In my classes, 9 and 10 year olds blow through such a low level of expectation within an (...) (18 years ago, 19-Jul-08, to lugnet.events.brickworld, lugnet.robotics)
| | | | | Re: NXT-G print to text?
|
| (...) It would really help to be able to read text. Specially when a young student brings me an NXT-G program for debugging that has switches buried within switches and loops, etc. It's really irritating when terminal points are lost while browsing (...) (18 years ago, 18-Jul-08, to lugnet.events.brickworld, lugnet.robotics)
|
|
