[Thread Prev] [Thread Next]
Thanks for all the suggestions Wendy, Jeff and Susan.
I am going to take Wendy's advice and attach two example projects; one
that I have been working on and another that belongs to a student. I
have figured out a work around for the stop command.
I have told the turtle
if touching? "t1 "t11 [t1, clickon announce [Click on any orange to see
its speed.] stopall]
This works but leaves a gap between the other girls and their oranges.
I wanted the oranges to stop when they reached their corresponding girl
and clickon their text of the speed.
My students and I are also experiencing a problem with and error that "
fd does not like  as input" from the moving_oranges or the testing
velocity procedure. Any suggestions? These errors will not allow the
project to run in presentation mode now.
Overview from a student point of view of the river trip
when we went to the river we wanted to see the physical qualities of the
river. So we tested turbidity, depth, width, velocity, and flow rate.
the turbidity was tested using a turbidity tube, depth with a meter
stick, width with measuring tape, velocity with oranges, and flow rate
using the calculations we had already had. I had only one problem with
MicroWorlds. My oranges wouldn't stop when I wanted them too. I still
haven't figured out why they won't stop. My project shows the velocity
test using the oranges.
Ms. S. Jackson
Middle School Technology Instructor
Young Women's Leadership Charter School
****Sorry Ms. Jackson****
**I am for Real**
[mailto:mwforum-admin@xxxxxxxxxxxxxxxxxx] On Behalf Of Wendy Petti
Sent: Tuesday, May 18, 2004 3:56 PM
Subject: RE: [MWForum]Help with Conditionals
I have some additional ideas to consider, to add to Jeff's and Susan's
I wonder if it is possible that the wrong turtle is stopping, and you
giving commands to a stationary turtle. You might consider being
about which turtle should stop.
Please also be aware that STOP only stops the procedure in which it is
found. If you have set the turtle into motion through a different
procedure, that procedure will not stop. This is why STOPALL (placed
*after* the announcement) would be a more foolproof stopping command.
If you want to isolate the difficulty, temporarily have something else
happen instead of asking the turtle to stop. For instance, remove the
command; is the announcement working? If so, then you know that the IF
command is checking properly for it has triggered the announcement. In
case, the STOP command is ineffectual, perhaps for the reason I've
suggested. But if the announcement is not triggered, then the IF
has not been checking continuously.
If you do not wish to run the procedure containing the IF command
continuously, you could also consider using WHEN instead of IF. The
structure is different so be sure to check the Help menu for details.
checks to see if the condition is true at one particular moment and then
stops checking; that is why you need to keep running the command. WHEN
keeps checking until the condition is true.
If you want to continue trying the colorunder method, be sure to
double-check the number of color over which the turtle will be passing.
don't know why, but on some projects in the past I've used a standard
to draw something but when I check its number later it might not be 35
instead 35.4 (or another decimal number).
Finally, if our collective advice has still not helped you to resolve
problem, *please send us the project as an attachment!!* We might be
to help you better if we can see exactly what is going on.
OWL's MicroWorlds in Action
> -----Original Message-----
> From: mwforum-admin@xxxxxxxxxxxxxxxxxx
> [mailto:mwforum-admin@xxxxxxxxxxxxxxxxxx]On Behalf Of Susan Einhorn
> Sent: Tuesday, May 18, 2004 2:54 PM
> To: mwforum@xxxxxxxxxxxxxxxxxx
> Subject: Re: [MWForum]Help with Conditionals
> On May 18 at 10:41 am, Mw. Jackson wrote:
> > I am in a real bind. I have introduced the conditional "if" to my
> > grade class. We have a BIG integration product due by Thursday for
> > Science/Tech Fair. The students are simulating their experience of
> > testing the velocity of water using oranges in a river. The orange
> > should stop either when it hits the rope or the girl shape.
> > Okay, here is the problem.
> > We wrote a procedure that that says
> > If touching? "orange1 "t2 [stop announce [.486 m/s]]
> > This is not working. The turtle is not reacting to the command.
> > ideas? I also tried using if colorunder = brown [stop announce
> > m/s]
> Here are some possible things to consider in addition to what Jeff has
> *The process that runs the conditional "if" must be running while the
> turtle is moving so that the condition is constantly being tested. Use
> forever or a button set to forever to make sure the process is running
> the turtle is moving.
> * To stop the turtle, you could use "clickoff" if the turtle is
> onclick instruction. Or you can use stopall in (or out of) the
> That stops everything.
> *Use the color number, not the color name with colorunder (eg, if
> = 35 [announce [This color is brown] stopall]
> Hope that helps,
> MWForum mailing list
> Attachments archived at:
> To unsubscribe or for administrative questions contact
Description: Binary data
Description: Binary data
Previous by thread:
Help with Conditionals
Next by thread:
Help with Conditionals
To save an attachment to your computer, PC users should right-click (Mac users, click and hold the mouse button) on the link and then choose 'save target as' from the pop-up menu. A window will then pop up in which you can choose a location for the file.