At 07:57 �� 9/1/2002 +0100, you wrote: >On Wed, Jan 09, 2002 at 04:35:12PM -0000, Dilwyn Jones wrote: > > > > > > >Phoebus R. Dokos wrote: > > >>>What, the driver? Not really. > > >> Wrong question... what I meant is... is it read (the status of the > > mouse) > > >> at the same addresses as QIMI ? > > > > > >Certainly, if you're using a QIMI interface. But not on QPC, Q40, > > QXL... > > > > > >Marcel > > > > Is there a way to directly read the pointer position [take the example > > of a screen saver program which is displaying a screen saver module > > (external program) but needs to monitor the mouse to see if it's been > > moved in order to to restore the screen] which is compatible across > > all or most platforms. Reading the QIMI registers will obviously only > > work in QIMI systems! Cuedark and a screen saver program from Thierry > > seem to do this but no documentation. The Jonathan Hudson Qeyes > > program also seems to allow a program to monitor pointer position [to > > position its own 'eyes] without affecting the currently active job. > >get it from the scr/con driver, it is at 0x20 and 0x22 offsets off the >base of the screen driver linkage block, the one cdb+4 should point >to. Not quite sure now if the 0x18 has to be added or not.. try >a few peeks.
Hmmm another undocumented feature... nothing in the SMS reference manual :-) Or at least I didn't see it. Thanks Richard Phoebus >Bye >Richard
