Advise needed on a couple of Raspberry Pi problems

Hi,

I’ve had a couple of RPi both with ROOl SD cards for a few of months now and I’ve got a few things I could do with help on.

Firstly the mouse. One of my RPIs has a wireless keyboard and mouse, the other has a plain usb mouse. Both suffer the same problems. I have great difficulty getting double click to work at all. It seems to need the two clicks to be so rapid I can’t actually do it. I’ve examined the mouse settings and played with the double click delay setting but this doesn’t seem to help my problem. I also have another mouse issue and this is some sort of auto repeat that I’ve never seen before. Say if I’m adjusting an OS setting like double click delay and I repeatedly click an up or down icon, at some point the machine takes over and carries on stepping long after mouse clicks have stopped.

For me, these two issues make using RPI almost impossible. Having never used a ROOL version of RISC OS before, I am concerned that both of these mouse problems may be intentional. Hope someone can tell me how to get more normal mouse behaviour.

My final problem is very slow copying to a NAS using the latest Lanman98. It is far slower (5x) than a standard SARPC but strangely, ShareFS copying to an RPC is fine. Any suggestions why?

Thanks guys for any help and suggestions.

Bob.

Very occasionally the USB system fails to spot a ‘key up’ event (and the released key just repeats) – this happens on both RISC OS and Linux on the Pi. It also happened on the Iyonix once or twice. The mouse button is the same effect. I also have trouble getting a double-click to work every time – sometimes it is treated as a SHIFT-click instead (e.g. opening an application directory filer window instead of running it) but that can be overcome by changing the setting for a mouse click that is prolonged (which can be set so that a slow click does SHIFT-click). I had thought initially it might have been SHIFT ‘stuck down’ but it is this setting – now that I mention it, I can’t find where this setting is specified, so I’m not much help to you.

If you are adjusting an OS setting with a ‘clickable triangle’ up/down icon, then you just need to hold the mouse button down, not keep clicking it.

I think the latest ROM allows the remote machine to create the large file before the data are copied over, rather than sending a file full of zeroes before starting the copy. Not sure whether LanMan98 does?

Hi Chris, thanks for trying to help.

I have mixed feelings about your comments above. You say this happens to you occasionally whereas I would say that very occasionally you can get a double click but you need a lot of patience to get there. However, if your setup is considerably more useable than mine that is good news as it may mean mine can be improved.

Can anyone think of any setting I could try or know if the Logitech k260 wireless keyboard and mouse is particularly bad for this?

Is there any hope it can be fixed?

Bob.

I have the Logitech MK320 wireless keyboard and mouse which suffers from the problem but not to a large degree. I asked around very carefully before buying as I knew some wireless setups would not work at all and others were very unreliable.

If you are getting a SHIFT-double-click when you were trying for a double click, then there is a setting which can sort this out – RISC OS can treat a ‘mouse button double-clicked and held down for a bit’ event as a SHIFT-double-click. This can mean that a double-click to run an application will actually open its filer window or a double-click to run a BASIC programme will open the file in an editor.

See also this post where it refers to ‘double-click and hold’. If you (successfully!) double-click !Boot and then click ‘Filer’ check that ‘Double-click and hold’ is NOT ticked. I have a ‘vanilla’ RC8 set up and this option was ticked.

Also, and this is counter-intuitive, try double-clicking slightly more slowly (to give the system time to notice that the mouse button has been released). The OS setting for double-click delay is the maximum amount of time between two clicks for them to be considered as a double-click (default one second). The USB stack is a compromise and it is interrogated using a substantial portion of the available processor bandwidth to try to capture every key up/key down event so that none are missed. Linux has the same issue.