The RCX display is a powerful tool for receiving feedback from different
programs. Often times, however, it is necessary to monitor more than
one variable at the same time. One solution to this problem is to
use a program similar to the one above.
The code above is designed to give feedback on two touch sensors.
The first step is to zero all relevant containers.
Remember, since containers are also global, old values from earlier
tests could still be stored, so zeroing them is essential. Next,
a task split is used to monitor the two touch sensors separately.
Each branch of the split waits for its touch sensor to be pressed,
adds either 1 or 100 to the red container, and then waits for the
sensor to be released. Thus the total clicks of touch sensor 1 will
be displayed in first two digits of the display, and the total clicks
of touch sensor 2 will be displayed in the last two digits of the
display. This code can be adapted to show any kind of sensor value,
including light or rotation. If the variables are in seperate containers
in the program, just multiply one container by a constant so that
it will display in the hundreds or thousands place on the display.
Then just add the two contatiners together in a thrid container
and display that value.
Just like single events, multiple events can be setup in the same
code to track different variables. The only difference is that all
event structures must have the same event landing. This means that
if 3 events are setup and only one triggers, the code will have to
determine which one of the 3 changed so it can perform the appropriate
action. In this example, two push events are used to control the motion
of a car. After setting up both events, monitoring is started and
the code is forced into an infinite loop. This is done to prevent
the code from reaching the event landing block prematurely. If the
red event (touch sensor 1) is triggered, the code will take the upper
path in the event fork and stop motor A. If the red event was not
triggered, then by default, the blue event must have been triggered
and the code will take the bottom the path of the fork. Three or more
events can be checked by increasing the number of event forks.
