The Sinclair QL Forum

This is probably covered somewhere! Hopefully…

I’m running QPC2 5 under a WIN10 set up and trying to use the mouse within a SuperBASIC Prog. In the past I recall the mouse movements being the same as cursor movements left/right/up/down (codes 192/200/208/216) and Spacebar (code 32) the left mouse button and Enter (code 10) the right mouse button.

All I get is a response from the right mouse button (code 10) and surprisingly the centre wheel with codes 209/217.

Mouse clicks on the QPC2 toolbar and menus are OK.

QBITS

qbits wrote:This is probably covered somewhere! Hopefully…

I’m running QPC2 5 under a WIN10 set up and trying to use the mouse within a SuperBASIC Prog. In the past I recall the mouse movements being the same as cursor movements left/right/up/down (codes 192/200/208/216) and Spacebar (code 32) the left mouse button and Enter (code 10) the right mouse button.

All I get is a response from the right mouse button (code 10) and surprisingly the centre wheel with codes 209/217.

Mouse clicks on the QPC2 toolbar and menus are OK.

QBITS

What you describe is a mouse driver that does cursor key emulation (Qimi used to do this, and I think SerMouse could be made to do it). Cursor emulation is, to my knowledge, not implemented in QPC2 (nor in any SMSQ/E computer).

If you want to use the mouse from S*Basic, you should be using the QPTR Toolkit or similar. (I think there is a hack that PEEKs the current mouse cursor position from the channel definition block(?), but I wouldn't really recommend doing that.

To use the mouse from BASIC you need extra toolkits. Qptr is the original pointer toolkit. Its a hard swallow and will probably change your life forever. EasyPointer is, as the name suggests, somewhat easier to get to grips with, not least of all because much of the hard work of creating and then managing menus, sprites and the like is done in a more graphical rather than textual way.

If you mainly want to stick with the old way of doing things, but want to add a little spice here and there, ie use the Pointer Interface only and avoiding the Window Manager, you could do worse than use some of the commands found at Knoware.no-toolkits-Pointer Environment. There are free-standing commands to read and set the pointer, set the Outline (for Qdos users), etc.

Even so, youre unlikely to get away without reading up on some aspects of the PE. No doubt, someone will pipe up with the best place to start, if anyone needs to know. (I write this without prejudice to how much you already know or dont know of the matter; there may be others reading this who could use the info..)

If it's only about reading the pointer position and mouse buttons, both QPTR and EasyPtr are relatively easy to handle.

QPTR: The "Termination vector" is in this example is set to "Pointer in Window OR Pointer outside window", thus RPTR returns immediately (you can set it to various other conditions) and sets the pointer position and button values in xabs% and yabs% accordingly.

EasyPtr is very similar: Here you'd do it like that:

Thanks for raining on my picnic So heres me blowing my own trumpet:
Uses Knoware's RPT% (376b, as opposed to Qptr's 9,620b, or EasyPointer's
15,442b.) Its all about what you want to do and who your target audience
is. I expect most high end users will have one or both of the PE toolkits
installed, in which case using one of them implies 0b overhead, but I
suspect the target audience here is somewhat less "bleeding edge", although
I may very well be wrong.

tofro wrote:What you describe is a mouse driver that does cursor key emulation (Qimi used to do this....)

No, only rudimentary if you keep pressing the left button. But that doesn't really do anything for programs. Far too difficult.

RalfR wrote:[No, only rudimentary if you keep pressing the left button. But that doesn't really do anything for programs. Far too difficult.

I thought I remember doing that long ago (when I tried it in SMSQmulator today it didn't work). But it was handy to quickly move cursor about in text editors (other than QD).

qbits wrote:I’m running QPC2 5 under a WIN10 set up and trying to use the mouse within a SuperBASIC Prog. In the past I recall the mouse movements being the same as cursor movements left/right/up/down (codes 192/200/208/216) and Spacebar (code 32) the left mouse button and Enter (code 10) the right mouse button.

All I get is a response from the right mouse button (code 10) and surprisingly the centre wheel with codes 209/217.

The left mouse button is normally used to move the cursor (i.e. produce the cursor keys you want). However, QPC adopts the absolute coordinates from windows for a seamless integration, the cursor movement is produced from relative coordinates (earlier QPC versions did this differently and it sucked). This is why the generic cursor keys code doesn't work anymore.

The code that is produced by the middle mouse button (/wheel) can be changed using the MOUSE_STUFF command.

So the function with the left button no longer works in QPC2, if I understand correctly.
It would be nice if there was such a cursor emulation (like SERmouse), the mouse moves the cursor normally. That would be nice for graphics programs without PE.