Hendrik Tews wrote:

Corne Beerse <[EMAIL PROTECTED]> writes:

  For current situations, I think there are some parties that have to
  cooperate:
  - The mouse driver at the console needs to send the signals to the
  desktop-s X11 (or msWindows desktop). I bet most standard mouse
  drivers only recognize 3 physical buttons and the scroll-wheel.

I don't know about the standard mouse drivers. I use evdev on
linux, which sends events for all buttons.
Is this the linux mouse driver or the X11 mouse driver? The linux mouse driver has to accept the calls and forwards it to the X11 mouse driver.

  - Then the window manager (linux or windows) must send the signals to
  the vncviewer application.

Under X it's not the window manager but the X server which
controls the mouse device. For the xorg server, the events are
available, xev does report them. So I guess the vncviewer sees
the events.
Under X11, the mouse-events the X11 server receives from the linux mousedriver must be passed on to the window manager. Finally, this windowmanager can handle the mouse-events itself or pass it on to the applications.

  - I guess the vncviewer application blindly sends all signals to the
  vncserver side.

How can I see what is sent? I tried -log '*:stderr:100' on both
vncviewer and vncserver. I do see key events in the server log,
but I don't see mouse events neither in the server log nor in the
viewer log.
there are X11 based tools that can monitor the X11 events. With them you can see if the events come to the other side. I donnot know if vnc has monitor options for these events. I see you have xev, that's such a tool.

  - msWindows based vncserver must send the signals to the remote
  msWindows windowmanager.

I am using linux on the viewer and the server side.

  - unix based vncserver (Xvnc) must handle the signals: send it to the
  windowmanager at that side and so on.

You mean the X server inside vncserver. That's definitely not
happening, otherwise I could see the events with xev inside vnc.
Then you have bad luck. Keep in mind that Xvnc (the binary called from the vncserver script) is a limited X11 server by itself. Actually, it is not limited as an X11 server but I can tell you, it has not much optional items available.

  - Finally there is the application that has to handle the mouse buttons...

There are enough applications that support more than 5 buttons:
emacs, firefox, gimp,...

So in my case everything but vnc supports more than 5 buttons.

That's bad luck. You can try if on of the vnc-alternatives (tight-vnc, true-vnc,...) does provide more than 5 buttons.


Bye,

Hendrik
_______________________________________________
VNC-List mailing list
[email protected]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
_______________________________________________
VNC-List mailing list
[email protected]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to