| From: | David McMinn |
| Date: | 17 May 2000 at 11:46:07 |
| Subject: | Re: New Command Set :-( (aaarrrggggh) |
Hi Stevie
> If you do the same thing using 'New Command Set', you will only get 2 mouse
> move messages ever. You can solve this by using a SetMouseQueue_ command
> but you have to supply a maximum amount of mouse events to store. i.e
> SetMouseQueue_ 255, but what use is this?
SetMouseQueue_ tells intuition how many mouse move events (maximum) you want in
your queue of window events *waiting* to be processed. So if you have 5 mouse
move events that you have not done anything with (i.e. you're doing something
processor intensive and you haven't reached the waitevent command before 5
mousemoves have been sent) then intuition will not send you any more until you
take some out of the queue, with a (wait)event type command.
> Does anyone know wether this is a bug in the 'New Command Set' libraries or
I think its a bug in the NCS. I tried opening an NCS window and then using the
OS commands to process the messages, and it still only gave me 5 mousemoves.
Changing to opening the window with OS commands gives the correct response -
mousemoves until you quit.
I don't know any workaround, I thought using OS commands for processing the
messages would have helped, but it seems not.
---------------------------------------------------------------------
To unsubscribe, e-mail: blitz-list-unsubscribe@netsoc.ucd.ie
For additional commands, e-mail: blitz-list-help@netsoc.ucd.ie