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. - 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. - 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. - 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. - 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. Bye, Hendrik _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
