Subject:
|
Re: Events in Robolab
|
Newsgroups:
|
lugnet.robotics.rcx.robolab
|
Date:
|
Sun, 28 Dec 2003 22:15:14 GMT
|
Reply-To:
|
brainchild@skylerANTISPAM.com
|
Viewed:
|
10629 times
|
| |
|
|
Thanks for the response. I've been to that web site before and looked
through it for event-driven programming. There is very little
event-driven programming there, and what there is doesn't use events
very extensively or in a very complex way. Considering the large
amount of very complex code there, I think this indicates they didn't
find event programming as productive as other methods. Possibly they
found some problems or limitations with events in Robolab also.
I rewrote my event-driven test program a half-dozen times, trying
different structure organizations (nested loops, a single event
landing for the entire program, etc.) and it never worked reliably.
Event monitoring begun inside a loop would detect the events during
some iterations, and ignore them during others (not necessarily in
that order). I rewrote it without events today and it worked
perfectly. It came out simpler that way also, so event-driven was
probably not the best paradigm for this program.
One aspect which may have been significant is monitoring for multiple
events at the same time; another is choosing which groups of events to
monitor based on which event fired from a previous multiple event
monitoring; a third possibility is repeatedly starting monitoring
inside a loop.
While I was dwelling on the fundamental interconnectedness of all
things on Sun, 28 Dec 2003 20:46:11 GMT, "Bill Blackmer"
<bill@bbccd.org> wrote:
> Don,
>
> Here is great site known for providing great examples of Robolab coding.
>
> http://www.convict.lu/Jeunes/RoboticsIntro.htm
>
> You will see several examples of event coding in this Web site.
>
> Bill
>
>
>
> -----Original Message-----
> From: news-gateway@lugnet.com [mailto:news-gateway@lugnet.com] On Behalf Of
> Don Stauffer
> Sent: Sunday, December 28, 2003 8:22 AM
> To: lugnet.robotics.rcx.robolab@lugnet.com
> Subject: Events in Robolab
>
> After dozens of hours of experimentation, it is my conclusion that
> event-driven programming in Robolab is unreliable. Eventually, the
> RCX stops responding to events. This does not always happen at the
> same point in a given program, nor is it predictably always associated
> with particular program constructs.
>
> Having not attempted event-driven programming of the RCX in another
> environment, I have not determined whether the fault is with Robolab
> itself, with the firmware, or with the RCX. I suspect a flaw in
> Robolab.
>
> Has anyone succeeded in using events in Robolab?
|
|
Message has 1 Reply:
 | | Re: Events in Robolab
|
| (...) I use Robolab to teach middle schoolers about building and programming Lego robots. I like Robolab because the kids pick up on the icons very quickly and get a handle the basics of programming within a few class sessions. BUT I do not venture (...) (21 years ago, 31-Dec-03, to lugnet.robotics.rcx.robolab)
|
Message is in Reply To:
| | RE: Events in Robolab
|
| Don, Here is great site known for providing great examples of Robolab coding. (URL) will see several examples of event coding in this Web site. Bill -----Original Message----- From: news-gateway@lugnet.com [mailto:news-gateway...ugnet.com] On Behalf (...) (21 years ago, 28-Dec-03, to lugnet.robotics.rcx.robolab)
|
8 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
