SwizzyFPS / android-vnc-viewer

Automatically exported from code.google.com/p/android-vnc-viewer
0 stars 0 forks source link

Suggestion for mouse input mode #209

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
This is a suggestion for another mouse input mode which I believe will result 
in a better overall experience since it combines panning and mouse movement 
into one action. It would allow fast movement of the mouse, but still allow 
finegrained control at the same time by utilizing concepts which we are already 
used to.

I am new here, so I appologize if this has already come up somewhere else.

The core concept is to always keep the mouse pointer in the center of the 
display on the android device. When you pan, the mouse also moves. It would be 
preferable to use a marker on the client side in addition to the mouse pointer 
that is streamed from the server to make it more visible.

This is not the same thing as the mouse follows pan feature already available, 
since that one only warps when the pointer is moved outside the screen.

There are two issues with this input mode: First is the ability to use mouse 
buttons. I suggest onscreen buttons at the bottom of the screen. Other 
alternatives could be physical buttons or tapping (the last of which I myself 
am not a fan of.)

The second issue is how to move the mouse to the edge of the screen (server 
side.) I can see two options here, the first one is to allow panning to outside 
the screen on the client side so that you can fill half of the screen with 
black. I don't know how these things are implemented in the client, so it might 
be hard. But I think this would work really well from a user experience 
perspective.

The other option I can come up with is moving the mouse from the center of the 
screen when approaching the edge. I am unsure how usefull this will be since it 
might be counterintuitive.

I have seen features similar to this in other android VNC viewers where an 
on-screen device could be moved around the screen and would follow when 
panning. But this would be a bit different from that.

Original issue reported on code.google.com by ank...@gmail.com on 3 Jan 2011 at 1:29