"shouldn't a team be praised for being creative? "
Absolutely!  It sounds like they considered using the touch sensor but 
then came up with the "delay" solution because of time constraints.  So 
I applaud them for being innovative on their own.

Let me share with you another solution which has been made available 
here on the listserv was well as other publicly available sites.
Combining missions is often done with a switch block with the "Sensor" 
property set to "NXT-buttons sensor".   The kids can then put their 1st 
mission on the switch statement's  top beam which ,say, corresponds to a 
left button press.    On the switch statement's bottom beam, one can 
nest another switch statement that includes the 2nd mission to kick off 
upon pressing the  right-button.
Don't forget to rap the whole program in and infinite loop because the 
program needs to keep checking for a left or right button press.

Feel free to introduce this to your team at your discretion ( maybe next 
season if time does not permit).  I would recommend doing it as an 
exercise completely out of the context of the challenge and to use 
leading questions to have the kids incrementally build a solution.

If others have seen alternative solutions please feel free to share....

Cheers
David ( VADCFLL Education Director)  Levy




Steven Pantaleo wrote:
> This is legal... as long as the robot is completely in base before it 
> starts moving again.
> Steven Pantaleo
>
> --------------------------------------------------
> From: "Annette Holloway" <[log in to unmask]>
> Sent: Thursday, November 13, 2008 10:21 AM
> To: <[log in to unmask]>
> Subject: [VADCFLL-L] Moving robot in base while program pauses
>
>> I have a mission question.
>>
>> Is it legal to start mission #1 from base (touch the brick to start 
>> the program),
>> have it do mission #1 COMPLETELY,
>> have it automatically come back to base (or it never leaves the base),
>> (the program then pauses for 3 seconds while the driver repositions 
>> the robot for the next mission and lets go without initiating another 
>> program),
>> then the robot performs mission #2 by going out of and coming back to 
>> base?  (A touch sensor is not an option right now)
>>
>> The driver would be touching the robot in base while the program 
>> itself pauses autonomously - the driver would not have to press a 
>> button to initiate the next program.
>>
>> I would think this could be done for all missions if a team wanted to.
>> Then they would have one big program and not have to hit any buttons 
>> if they timed the transition correctly.
>> Instead of being illegal, shouldn't a team be praised for being 
>> creative? :)
>>
>> Annette Holloway
>>
>> ______________________________________________________________
>> To UNSUBSCRIBE or CHANGE YOUR SETTINGS, please visit 
>> https://listserv.jmu.edu/archives/vadcfll-l.html and select "Join or 
>> leave the list".
>>
>> If you want to join the VADCFLL-ADMIN-L mailing list - to which FLL 
>> administrative announcements will be distributed - visit 
>> https://listserv.jmu.edu/archives/vadcfll-admin-l.html and select 
>> "Join or leave the list". 
>
> ______________________________________________________________
> To UNSUBSCRIBE or CHANGE YOUR SETTINGS, please visit 
> https://listserv.jmu.edu/archives/vadcfll-l.html and select "Join or 
> leave the list".
>
> If you want to join the VADCFLL-ADMIN-L mailing list - to which FLL 
> administrative announcements will be distributed - visit 
> https://listserv.jmu.edu/archives/vadcfll-admin-l.html and select 
> "Join or leave the list".

______________________________________________________________
To UNSUBSCRIBE or CHANGE YOUR SETTINGS, please visit https://listserv.jmu.edu/archives/vadcfll-l.html and select "Join or leave the list".

If you want to join the VADCFLL-ADMIN-L mailing list - to which FLL administrative announcements will be distributed - visit https://listserv.jmu.edu/archives/vadcfll-admin-l.html and select "Join or leave the list".