| |
In lugnet.robotics.rcx.robolab, Elizabeth Mabrey wrote:
> > firmware... You can monitor multiple events, but only in
> > *different* tasks. In other words, (to my knowledge) you can
> > not "nest" event monitors.
>
> Hmm..., notice that the start monitoring icon allows to
> watch for multiple events within the same task. If each
> task can only monitor a single event, that feature being
> there does not quite make sense.
Yeah, my fault. I said two things that do not have to follow. Yes, you can
use one event monitor to watch more than one event... and yes, you can't nest
event monitoring statements. I've not used an event watcher to monitor more than
one event previously.
> ....if only one event monitor can take place in
> a single task
Then you use one monitor to watch for multiple events. The trick is
determining which event(s) fired to trip you into the event handling branch. In
NQC there's a command to interrogate the firmware to determine which event(s)
have fired after the fact - the question now becomes, where in Robolab does such
a command exist?
> I always create comment as synopsis at the
> top of my robolab vi file.
Sigh. I wish I had the time to understand Robolab better. Seems like a
wonderful language (especially for my 7-year-old) but the enviroment really put
me off when I started in with it.
--
Brian Davis
|
|
Message has 1 Reply:
Message is in Reply To:
5 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
|
|
|
|
