Re: [MiNT] XaAES (fwd)

[Henk Robbers <h.robbers@chello.nl>]

Petr Stehlik wrote:
>
> 
> If you don't understand why then ask the original author. That's the
> best idea, I think.
> 

Olivier is right that there is a sync problem when using vq_mouse.

Please look in the small functions in kernel.c

no_mouse
have_mouse
get_mouse

They keep track of XaAES's knowledge of the mouse.
If vmoose reports a mouse button event, this is recorded in have_mouse and
vq_mouse isnt called in get_mouse.

Notes:
vex_butv is only gone thru when the button state changes.

Many AES events, not only MU_BUTTON, supply mouse state and position.
evnt_button and evnt_multi(MU_UTTON) must fall thru when the vutton state
matches the masks.
:setoN

In those cases (when the state hasnt changed)
I used vq_mouse (in get_mouse) to get the information.
If you can be sure that vmoose never misses a state change (a dangerous and not
fail safe assumption) you can keep track of the current state without
calling vq_mouse. Thats what the above small function can be changed to.

I decided not to take the risc; I could very well spend
most of my time getting GEM programs run at all. ;-)


-- 
Groeten; Regards.
Henk Robbers.    mailto:h.robbers@chello.nl
                   http://members.ams.chello.nl/h.robbers/Home.html
Interactive disassembler:     TT-Digger;  http://digger.atari.org
A GEM replacement for MiNT:   XaAES;      http://xaaes.atari.org
A Home Cooked teXt editor:    AHCX
The free desktop:             TERADESK