Hi Norman, > Well my experiments, granted very simple, show the LSB ony is non-zero the > remainder are zero. Mind you, how exactly do I send an event to a job? > > Use the "send_event" keyword. (send_event job_id,events) > If I PICK the job, or button frame it, then DO it's button, I get the same > event both times - $2D with a Key Stroke of $08. > > Which would be a wake.
> <SNIP bitmap details> > > Interesting. If I position the pointer exactly on 0,0 and simply press a > key (including space and enter) I still get the pointer moved bit set. > > Strange > I tried repeatedly pressing the same key when the pointer was stationary > - I always get 'the pointer moved', as follows : > > xorg yorg eventvec ks kd > 0000 0000 0000002B 01 01 <- Pressing SPACE key without moving pointer > 0000 0000 0000002B 02 02 <- Pressing ENTER key without moving pointer > 0000 0000 0000002D 66 00 <- Pressing 'f' key without moving pointer. > > And so on. > > So my $2B (0010 1011) is as above, Keystroke in window + > keypress in window + Pointer moved + Pointer in window. > > And my $2D (0010 1101) is Keystroke in window + Key up in Window + > Pointer moved + Pointer in window. > > Yeah, well, you'll probably get key down & up "randomly" depending on whether, when you get out of the read loop, a key was pressed still or not. > Both showing that the pointer moved event took place, but the pointer > coordinates never changed. In addition, in my call to IOP_RPTR, I set the > initial coordinates to 0,0 each time around the loop - it never affects > the pointer position - as far as I can see that is! However, I'm willing > to be convinced that internally it is setting them to 0,0 and then > resetting them to the current pointer position - but I honestly don't > know. > > I haven't checked that, either. (...) > > FYI, this is the code I'm currently playing with : > (...) OK, thanks, I'll give it a spin this weekend. Wolfgang _______________________________________________ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
