search

dmwhw / android-vnc-viewer

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

Can't pan or align on VNC server geometries below device resolution #265

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
I am running Android vnc on a 800x600 PanDigital tablet.  This tablet does not 
have any non touch input; I am using touchscreen pan for this experiment.

I'm running a dedicated VNC server session for the touchpad to get access to an 
application that does not run on Android.  As such, I'm adjusting the server 
geometry to fit the tablet device.

When I run a 1280x1024 resolution pan operates as expected.  If I run 800x800 
pan also operates as expected with only horosontal panning operating.  However, 
on 800x600 and below I cannot pan.  This is probably by design, as the window 
should fit the display.

I am trying to pan because the viewer cuts off the bottom of my window with the 
taskbar.  (I don't know what that is called on Android, a quick google got me 
nowhere.  Hope you follow.)  I was attempting to run a lower resolution to 
circumvent this (800x550 or such), however when the horosontal server 
resolution is lower than the native screen resolution the viewer seems to pad 
with a bar at the top, still leaving the bottom of the display blocked.  A test 
at 800x200 shows the bottom of the display blocked, with a large black bar at 
the top.

Quickest satisfactory resolution here would be to align the VNC window to the 
top of the screen, not the bottom.  A better solution would be to omit the 
space used by the taskbar when calculating the screen resolution and then use 
that value for the pan/zoom code.

Original issue reported on code.google.com by t...@tjnii.com on 22 Sep 2011 at 3:02

GoogleCodeExporter commented 8 years ago 
After procuring a Android phone I realized the "taskbar" I speak of seems 
limited to the buttonless tablet device I was originally using.  The "taskbar" 
implements the back, home, and config buttons on the screen as they don't exist 
on the device.  As such, this bug likely only manifests on buttonless touchpads.

Furthermore, due to the nature of the "taskbar" I mentioned there probably is 
not an easy way to detect it, nor code around it.  As such I recommend my 
window top alignment suggestion as a solution.  This will allow users who hit 
this to work around it via resolution fiddling while not diverting too much dev 
time to a bug with limited hardware impact.

Original comment by t...@tjnii.com on 27 Sep 2011 at 3:38