Is it possible that the button that causes the problem is the last one
(or first one - i.e., a boundary condition)? If so, try adding a
"dummy" number to the end or beginning of the list and see what happens.
len morgan
It's nothing clever - just an mouseUp
with generic code which is used by
a number of other buttons - which all
work. Just a matter of checking if the
label "12" is in a list "10,11,12" and
acting accordingly. It was in the list
and the other numbers were found.
As I said, it ran OK in the IDE so it's
something that happens during
compiling.
/quote
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
