While using the evnt_multi call, I encountered
a weird behaviuor of the mouse. I wonder if
this is a known bug (I'm using TOS 1.0), or
that I am missing some thing. (I hope for
Here is what happens:
Using evnt_multi, in a loop I sollicit for keyboard-input
evnt_multi( MU_KEYBD | MU_BUTTON , .... );
This works fine for a while, but when the mouse is moved
to the menu-bar (that is still enabled when this code
is executed), afterwards mouse-clicks are not detected
anymore. The same thing happens when the mouse is moved
to the 400th line of the display.
I considered that maybe I should call
menu_bar( menu, 0 )
first. This helps a little, in that mere moving the
mouse to the menu-line is harmless now. Clicking on the
menu-line however is as fatal as it was before: instead of
reporting a mousclick for this click, all future mouseclicks
The keyboard-events are still being reported. If, in the
process_input part of code, a form-alert is called, afterwards
everything is normal again.
What magical clean-up call is it, that re-enables the
mouseclicks? I am willing to call it before every evnt_multi,
if I must... desperate as I am...
But of course, if I am doing something fundamentally wrong,
I should like to know what that is, too. All help is welcome!
dept.of Computer Science, Utrecht University | tel.+31-30-534129
PObox 80089, 3508TB Utrecht, the Netherlands | fax.+31-30-513791