This fixes the right mouse button problem for us! Environment: vnc-3.3.3r2 on SunMS Unix Solaris 7, Solaris 8.
Many thanks for spotting the Motif tip. We are adding "*.whichButton: 3" to our site-wide login. FYI my Motif 2.1 Reference Manual (O'Reilly vol 6B) says this XmRowColumn widget resource is superseded by another (dissimilar)resource; I guess this ties up with the problem being observed only in libXm since Solaris 7. One thing which does not tie-up is my similar ctrl+mouse problem in openwin xterm(1), but I think that should be ignored: firstly, xterm(1) does not use libXm; second, the problem was different anyway; third, it has now "gone away" for an unknown reason :-( Copied to vnc-list for celebration :-) Freddy Jensen wrote: > > >From: adam <[EMAIL PROTECTED]> > >Date: Wed Feb 13 2002 2:14pm > >To: Adam Nevins <[EMAIL PROTECTED]> > >Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] > >Subj: Re: The vnc right-click problem > > > >Doh! I forgot to paste in the link. > > > >http://www.motifdeveloper.com/tips/tip21.html > > > >On Wed, 2002-02-13 at 16:34, adam wrote: > >> Just got this from a friend. He says it solved the problem. I hope > >> it's helpful. > >> > >> -Adam > >> > > Adam, > > Thank you very much for the info. > > I will look into it as soon as I get some spare time. > > -- > Freddy Jensen, Sr. Computer Scientist, Adobe Systems Incorporated > 345 Park Avenue, San Jose, CA 95110-2704, USA, Ph: (408) 536-2869 > Email: [EMAIL PROTECTED], URL: http://www.adobe.com > -- > > >> > >> > >> [EMAIL PROTECTED] wrote: > >> > >> > Hi, > >> > > >> > > >> > I wish I could say I had an answer, alas I'm just another poor soul > >> > looking for the answer. Have any of you found a fix/workaround? > >> > > >> > Could it be Motif? > >> > > >> > Our Motif app started exhibiting the problem when we went from Solaris > >> > 5.5.1 to 5.7. Turns out that the problem only happens when using the > >> > libXm.so from Solaris 5.7. I can get rid of the problem by buggering > >> > the LD_LIBRARY_PATH so it finds a copy of the 5.5.1 lib. > >> > Unfortunately, this is not an acceptable solution for us. > >> > > >> > The fast-returning/do-nothing libXt:HandleActions call might be > >> > explained by a subtle bug in Motif, e.g. one version doesn't care > >> > about a flag in the Xevent. > >> > > >> > Despite being able to tickle the bug with different Motif libs, it > >> > still seems that there must be *some* difference in the way Xvnc > >> > transmits the buttondown event to the client, compared to other > >> > Xservers. And since I have a better chance of getting this fixed in > >> > Vnc than in Motif, I'll do some more poking around here. > >> > > >> > Please let me know if you have any updates since this thread. > >> > > >> > Thanks, > >> > > >> > Adam Nevins > >> > > >> > > >> > > >> > Re: Mouse right-click problem > >> > > >> > * From:* Freddy Jensen (/ [EMAIL PROTECTED]/ > >> > ><mailto:[EMAIL PROTECTED]?Subject=Re:%20Mouse%20right-click%20problem&In-Reply-To=%3C001011105308.ZM10680@voyager%3E> > >> > ) > >> > *Date:* Wed Oct 11 2000 - 18:53:08 BST > >> > > >> > * *Next message:* Joe Knapka: "Re: Who has VNCView ActiveX?" > >> > <http://www.uk.research.att.com/vnc/archives/2000-10/0200.html> > >> > * *Previous message:* Mark Rainford: "RE: Mouse right-click > >> > problem" > >> > <http://www.uk.research.att.com/vnc/archives/2000-10/0198.html> > >> > * *Messages sorted by:* [ date ] > >> > <http://www.uk.research.att.com/vnc/archives/2000-10/date.html#199> > >> > [ thread ] > >> > <http://www.uk.research.att.com/vnc/archives/2000-10/index.html#199> > >> > [ subject ] > >> > <http://www.uk.research.att.com/vnc/archives/2000-10/subject.html#199> > >> > [ author ] > >> > <http://www.uk.research.att.com/vnc/archives/2000-10/author.html#199> > >> > > >> > > >> > ------------------------------------------------------------------------ > >> > > >> > / >From: Mark Rainford < [EMAIL PROTECTED] > >> > ><mailto:[EMAIL PROTECTED]?Subject=Re:%20Mouse%20right-click%20problem&In-Reply-To=%3C001011105308.ZM10680@voyager%3E> > >> > > / > >> > / >Date: Wed Oct 11 2000 10:16am / > >> > / >To: [EMAIL PROTECTED] > >> > ><mailto:[EMAIL PROTECTED]?Subject=Re:%20Mouse%20right-click%20problem&In-Reply-To=%3C001011105308.ZM10680@voyager%3E> > >> > / > >> > / >Subj: RE: Mouse right-click problem / > >> > / > / > >> > / >I have some additional information on this problem - which hopefully / > >> > / >will "ring a bell" with some X / VNC guru out there. / > >> > / > / > >> > / >Environment: Xvnc/vncviewer 3.3.3r1 and X clients all on SunMS > >> > Solaris 7 / > >> > / >Unix. / > >> > / > / > >> > / >Problem: several X applications fail act on some mouse but not all / > >> > / >Press/Release events - while yet other applications do not have the > >> > same / > >> > / >problem. / > >> > / > / > >> > / > / > >> > / >Here's what I can add .... / > >> > / > / > >> > . > >> > . > >> > . > >> > . > >> > > >> > This happens for me also. I have one particular application where > >> > the right mouse button is ignored. I run the VNC server on a Linux > >> > box. I run the viewer, either on the same linux box, or on a Solaris > >> > machine, or on an WinNT machine. The right mouse button is ignored > >> > for my particular application in all scenarios. I can also confirm > >> > that the window manager is not the problem. I run twm. When I exit > >> > twm the problem is still there, for my particular app, which is > >> > Motif-Zmail. Other apps, like Netscape, have no problems getting > >> > the right mouse button events. > >> > > >> >-- > >> >Freddy Jensen, Sr. Computer Scientist, Adobe Systems Incorporated > >> >345 Park Avenue, San Jose, CA 95110-2704, USA, Ph: (408) 536-2869 > >> >Email: [EMAIL PROTECTED] ><mailto:[EMAIL PROTECTED]?Subject=Re:%20Mouse%20right-click%20problem&In-Reply-To=%3C001011105308.ZM10680@voyager%3E>, > URL: http://www.adobe.com > >> >-- > >> > > >> > >A) the problem is the same without a window manager running so we can > >> > >forget the WM as an intrusive influence. > >> > > > >> > >B) The Xvnc server is definitely sending the BtnPress/Release events > >> > >(confirmed with /usr/openwin/demo/xscope), but there are also > >> > >interleaving Enter/Leave/Focus/Grab events which always seem to differ > >> > >(cos I have a shakey hand I guess). I have no skill to identify whether > >> > >these are a crucial difference. > >> > > > >> > >Does this mean we can also rule out the vncviewer are part of the > >> > >problem? > >> > > > >> > > > >> > >C) The problem different for different applications. > >> > > > >> > >C.1) I have a Motif application which is able to popup a menu in the > >> > >work area and arm buttons within it from Btn3Press+hold+MouseMotion; but > >> > >it fails to Activate popup menu button upon Btn3Release. The same fault > >> > >applies to Button2, but not to Button1 (!) Button1 works fine! > >> > > > >> > >C.2 Different buttons suffer in the openwin version of xterm(1): > >> > >normally each of mouse buttons 1,2,3 in conjunction with Ctrl will pop > >> > >up an xterm(1) control menu. Running on the Xvnc display Button3+Ctrl > >> > >pops up the "VT Fonts" menu - as expected; however, Buttons 1+2 behave > >> > >as if Ctrl was not held down (ie they do select and paste). > >> > > > >> > >C.3) My window manager (fvwm2) does not seem to suffer any loss of mouse > >> > >button Press/Release events: root window menus work fine. > >> > > > >> > > > >> > >D) A trace of libXt/libX11 calls in /usr/openwin/bin/xterm shows the > >> > >handling of the ButtonRelease being cut short in the failure case (Trace > >> > >made with Solaris truss(1) command line "truss -u 'libXt::*,libX11::*' > >> > >-o /tmp/root.truss.xterm -p 15146"). > >> > > > >> > >D.1) This is an extract from the working case: XtDispatchEventToWidget() > >> > >calls _XtTranslateEvent() which calls HandleSimpleState() which calls > >> > >HandleActions() which eventually reaches the callback which pops up the > >> > >xterm "VT Fonts" menu. > >> > > > >> > > -> libXt:XtDispatchEventToWidget(0x55f68, 0xffbef098, 0xffbef098, > >> > >0x0) > >> > > -> libXt:_XtConvertTypeToMask(0x4, 0x33fc8, 0x0, 0x0) > >> > > <- libXt:_XtConvertTypeToMask() = 4 > >> > > -> libXt:_XtTranslateEvent(0x55f68, 0xffbef098, 0x0, 0x0) > >> > > -> libXt:XEventToTMEvent(0xffbef098, 0xffbeeecc, 0x0, 0x0) > >> > > <- libXt:XEventToTMEvent() = 0xffbef098 > >> > > -> libXt:HandleSimpleState(0x55f68, 0x55f98, 0xffbeeecc, 0x0) > >> > > -> libXt:MatchBranchHead(0x574a0, 0x0, 0xffbeeecc, 0x0) > >> > > <- libXt:MatchBranchHead() = -2 > >> > > -> libXt:MatchBranchHead(0x5bbe0, 0x0, 0xffbeeecc, 0xff2d4000) > >> > > -> libXt:_XtRegularMatch(0x55ba0, 0x55c68, 0xffbeeecc, > >> > >0xff2a1858) > >> > > <- libXt:_XtRegularMatch() = 0 > >> > > -> libXt:_XtRegularMatch(0x55ba0, 0x55c78, 0xffbeeecc, > >> > >0xff2a1858) > >> > > <- libXt:_XtRegularMatch() = 0 > >> > > -> libXt:_XtRegularMatch(0x55ba0, 0x55c48, 0xffbeeecc, > >> > >0xff2a1858) > >> > > <- libXt:_XtRegularMatch() = 0 > >> > > -> libXt:_XtRegularMatch(0x55bb0, 0x55c68, 0xffbeeecc, > >> > >0xff2a1858) > >> > > <- libXt:_XtRegularMatch() = 0 > >> > > -> libXt:_XtRegularMatch(0x55bb0, 0x55c78, 0xffbeeecc, > >> > >0xff2a1858) > >> > > <- libXt:_XtRegularMatch() = 0 > >> > > -> libXt:_XtRegularMatch(0x55bb0, 0x55c98, 0xffbeeecc, > >> > >0xff2a1858) > >> > > <- libXt:_XtRegularMatch() = 0 > >> > > -> libXt:_XtRegularMatch(0x55bd0, 0x55c68, 0xffbeeecc, > >> > >0xff2a1858) > >> > > <- libXt:_XtRegularMatch() = 1 > >> > > <- libXt:MatchBranchHead() = 14 > >> > > -> libXt:GetTime(0x55f98, 0xffbef098, 0xffbeeecc, 0xff2d4000) > >> > > <- libXt:GetTime() = 0x243927f7 > >> > > -> libXt:FreeContext(0x55fa0, 0xffbef098, 0xffbeeecc, > >> > >0xff2d4000) > >> > > -> libXt:XtFree(0x0, 0x0, 0x0, 0x0) > >> > > <- libXt:XtFree() = 0 > >> > > <- libXt:FreeContext() = 0x55fa0 > >> > > -> libXt:MatchExact(0x5bbe0, 0xf, 0xc, 0x5) > >> > > <- libXt:MatchExact() = -2 > >> > > -> libXt:HandleActions(0x55f68, 0xffbef098, 0x5bbe0, 0x0) > >> > > -> libXt:XtWidgetToApplicationContext(0x55f68, 0x0, 0x0, > >> > >0x0) > >> > > -> libXt:_XtGetPerDisplay(0x4e930, 0x0, 0x0, 0x0) > >> > > <- libXt:_XtGetPerDisplay() = 0x53d74 > >> > > <- libXt:XtWidgetToApplicationContext() = 0x4e0d0 > >> > >write(3, "1701\002\0\0\001", 8) = 8 > >> > >read(3, "01\01D U\0\0\0\0\0\0\0\0".., 32) = 32 > >> > > -> libXt:XtSetValues(0x69c30, 0x44ad0, 0x1, 0x4d2b0) > >> > > -> libXt:XtWidgetToApplicationContext(0x69c30, 0x0, 0x0, > >> > >0x0) > >> > > -> libXt:_XtIsHookObject(0x69c30, 0x0, 0x0, 0x0) > >> > > > >> > >... carries on to do the application callbacks > >> > > > >> > > > >> > >D.3 This is an extract from the failing case: the same sequence of Xt > >> > >calls as above, except that HandleActions() returns very quickly, and > >> > >without calling the application callbacks: > >> > > > >> > > -> libXt:_XtTranslateEvent(0x56658, 0xffbef0c0, 0x0, 0x0) > >> > > -> libXt:XEventToTMEvent(0xffbef0c0, 0xffbeeef4, 0x0, 0x0) > >> > > <- libXt:XEventToTMEvent() = 0xffbef0c0 > >> > > -> libXt:HandleSimpleState(0x56658, 0x56688, 0xffbeeef4, 0x0) > >> > > -> libXt:MatchBranchHead(0x57538, 0x0, 0xffbeeef4, 0x0) > >> > > <- libXt:MatchBranchHead() = -2 > >> > > -> libXt:MatchBranchHead(0x5bc78, 0x0, 0xffbeeef4, 0xff2d4000) > >> > > -> libXt:_XtRegularMatch(0x55c38, 0x55d00, 0xffbeeef4, > >> > >0xff2a1858) > >> > > <- libXt:_XtRegularMatch() = 0 > >> > > -> libXt:_XtRegularMatch(0x55c38, 0x55d10, 0xffbeeef4, > >> > >0xff2a1858) > >> > > <- libXt:_XtRegularMatch() = 0 > >> > > -> libXt:_XtRegularMatch(0x55c38, 0x55d20, 0xffbeeef4, > >> > >0xff2a1858) > >> > > -> libXt:_XtComputeLateBindings(0x4e9c8, 0x63570, > >> > >0xffbeeda4, 0xffbeeda0) > >> > > -> libXt:_XtGetPerDisplay(0x4e9c8, 0x0, 0x0, 0x0) > >> > > <- libXt:_XtGetPerDisplay() = 0x53e0c > >> > > <- libXt:_XtComputeLateBindings() = 0 > >> > > <- libXt:_XtRegularMatch() = 0 > >> > > -> libXt:_XtRegularMatch(0x55c38, 0x55d30, 0xffbeeef4, > >> > >0xff2a1858) > >> > > -> libXt:_XtComputeLateBindings(0x4e9c8, 0x634b0, > >> > >0xffbeeda4, 0xffbeeda0) > >> > > -> libXt:_XtGetPerDisplay(0x4e9c8, 0x0, 0x0, 0x0) > >> > > <- libXt:_XtGetPerDisplay() = 0x53e0c > >> > > <- libXt:_XtComputeLateBindings() = 0 > >> > > <- libXt:_XtRegularMatch() = 0 > >> > > -> libXt:_XtRegularMatch(0x55c38, 0x55ce0, 0xffbeeef4, > >> > >0xff2a1858) > >> > > -> libXt:_XtComputeLateBindings(0x4e9c8, 0x5be78, > >> > >0xffbeeda4, 0xffbeeda0) > >> > > -> libXt:_XtGetPerDisplay(0x4e9c8, 0x0, 0x0, 0x0) > >> > > <- libXt:_XtGetPerDisplay() = 0x53e0c > >> > > <- libXt:_XtComputeLateBindings() = 1 > >> > > <- libXt:_XtRegularMatch() = 1 > >> > > <- libXt:MatchBranchHead() = 10 > >> > > -> libXt:GetTime(0x56688, 0xffbef0c0, 0xffbeeef4, 0xff2d4000) > >> > > <- libXt:GetTime() = 0x24b80adc > >> > > -> libXt:FreeContext(0x56690, 0xffbef0c0, 0xffbeeef4, > >> > >0xff2d4000) > >> > > -> libXt:XtFree(0x0, 0x0, 0x0, 0x0) > >> > > <- libXt:XtFree() = 0 > >> > > <- libXt:FreeContext() = 0x56690 > >> > > -> libXt:MatchExact(0x5bc78, 0xb, 0x9, 0x3) > >> > > <- libXt:MatchExact() = -2 > >> > > -> libXt:HandleActions(0x56658, 0xffbef0c0, 0x5bc78, 0x0) > >> > > -> libXt:XtWidgetToApplicationContext(0x56658, 0x0, 0x0, > >> > >0x0) > >> > > -> libXt:_XtGetPerDisplay(0x4e9c8, 0x0, 0x0, 0x0) > >> > > <- libXt:_XtGetPerDisplay() = 0x53e0c > >> > > <- libXt:XtWidgetToApplicationContext() = 0x4e168 > >> > > > >> > >*** exits too soon without reaching app. callbacks *** > >> > > > >> > > <- libXt:HandleActions() = 0 > >> > > <- libXt:HandleSimpleState() = 80 > >> > > <- libXt:_XtTranslateEvent() = 0x56658 > >> > > > >> > > > >> > >E) It seems to me that the problem is libXt's understanding of something > >> > >about the X server (ie Xvnc). I note the same problem has been reported > >> > >for different platforms; does this mean that some part of the X > >> > >client/Xvnc initial conversation is at fault ? > >> > > > >> > >F) Sorry for the long post. I hope somebody out there has just > >> > >experienced a light bulb turning on :-) > >> > > > >> > > > >> > > > >> > > > >> > >>From: Rob Treuer ([EMAIL PROTECTED] > >> > ><mailto:[EMAIL PROTECTED]?Subject=Re:%20Mouse%20right-click%20problem&In-Reply-To=%3C001011105308.ZM10680@voyager%3E>) > >> > >>Date: Thu Jun 22 2000 - 23:19:46 BST > >> > >> > >> > >> > >> > >>While I don't have a solution for you, I have some suggestions > >> > >>to help you debug the problem. > >> > >> > >> > >>[1] I would suspect the window manager to be guilty of intercepting > >> > >>the right-mouse button events, before suspecting the Xvnc server > >> > itself. > >> > >>If the problem shows up with a window manager running, and goes away > >> > >>when no window manager is running, there is probably something unusual > >> > >>in the set-up of the window manager. > >> > >>Let's say you use twm (or mwm, or olwm), then your "xstartup" script > >> > looks > >> > >>something like this: > >> > >>#!/bin/sh > >> > >>xhost + > >> > >>xrdb /user/somebody/.Xdefaults > >> > >>xsetroot -solid grey > >> > >>xterm & > >> > >>twm & > >> > >> > >> > >>Replace the line "xterm &" (or add another line after it), > >> > >>with the command for your program, such as: > >> > >>HP OpenView/Network Node Manager, or Zmail. > >> > >>Then delete the last line "twm &", which means that your program(s) > >> > will > >> > >>be the only thing(s) running, without benefit of a window manager. > >> > >>Then invoke your vncserver.pl script, and see if the problem still > >> > shows up. > >> > >>You can always add a window manager to a running X session, just type: > >> > >>twm -display myhost:2 >& /dev/null & > >> > >>After using it a while, you can kill it, and even replace it with > >> > >>a different window manager: > >> > >>olwm -display myhost:2 >& /dev/null & > >> > >>In fact, you can kill and restart the window manager for any currently > >> > >>running session, and Xvnc and all other X-clients should survive. > >> > >> > >> > >>[2] You can also remap the mouse button-events seen by Xvnc, using > >> > >>the "xmodmap" command. > >> > >>xmodmap -pp > >> > >>will show the current mouse pointer mappings. > >> > >>xmodmap -e "pointer = 1 3 2" > >> > >>will swap the middle and right mouse buttons, and > >> > >>xmodmap -e "pointer = 1 2 3" > >> > >>will restore the default button mapping. > >> > >> > >> > >>Regards, > >> > >>Robert. > >> > >> > >> > >>> -----Original Message----- > >> > >>> From: [EMAIL PROTECTED] > >> > ><mailto:[EMAIL PROTECTED]?Subject=Re:%20Mouse%20right-click%20problem&In-Reply-To=%3C001011105308.ZM10680@voyager%3E> > >> > > >> > >>> Sent: Thursday, June 22, 2000 3:44 PM > >> > >>> To: [EMAIL PROTECTED] > >> > ><mailto:[EMAIL PROTECTED]?Subject=Re:%20Mouse%20right-click%20problem&In-Reply-To=%3C001011105308.ZM10680@voyager%3E> > >> > > >> > >>> Cc: [EMAIL PROTECTED] > >> > ><mailto:[EMAIL PROTECTED]?Subject=Re:%20Mouse%20right-click%20problem&In-Reply-To=%3C001011105308.ZM10680@voyager%3E> > >> > > >> > >>> Subject: Re: Mouse right-click problem > >> > >>> > >> > >>> > >> > >>> >From: Bob Fulwiler <[EMAIL PROTECTED] > >> > ><mailto:[EMAIL PROTECTED]?Subject=Re:%20Mouse%20right-click%20problem&In-Reply-To=%3C001011105308.ZM10680@voyager%3E>> > >> > > >> > >>> >Date: Thu Jun 22 2000 12:20pm > >> > >>> >To: VNC Mail List <[EMAIL PROTECTED] > >> > ><mailto:[EMAIL PROTECTED]?Subject=Re:%20Mouse%20right-click%20problem&In-Reply-To=%3C001011105308.ZM10680@voyager%3E>> > >> > > >> > >>> >Subj: Mouse right-click problem > >> > >>> > > >> > >>> >Good Day Folks, > >> > >>> > > >> > >>> >I have a situation which I am hoping you can help me with. > >> > >>> > > >> > >>> >Environment: vnc servers running on solaris 2.6; vnc > >> > >>> viewers running on > >> > >>> >solaris, WinNT, and > >> > >>> >Win95/98. Main application is HP OpenView/Network Node Manager. > >> > >>> > > >> > >>> >Problem: When users right-click on an Openview map object (host, > >> > >>> >router, etc.), they shoul be > >> > >>> >presented with a dialog showing certain object > >> > >>> properties. This works > >> > >>> >just fine in a native OV > >> > >>> >window. However, with VNC, the right click produces no > >> > >>> results. It > >> > >>> >seems that the OV application is > >> > >>> >not receiving the mouse event. > >> > >>> > > >> > >>> >Has anyone had a similar proble? If so, how did you solve it? > >> > >>> > > >> > >>> >Thanks, > >> > >>> >Bob > >> > >>> > > >> > >>> >-- > >> > >>> >Bob Fulwiler > >> > >>> >UNIX System Administrator > >> > >>> >425 865-4712 > >> > >>> >Bellevue Site Operations > >> > >>> > > >> > >>> > >> > >>> > >> > >>> I have the exact same problem. I run the Xvnc server on a linux > >> > >>> machine. I connect with a viewer from either an NT machine, or > >> > >>> sometimes I run a simple X session on the same machine (the Linux > >> > >>> box) and run the viewer there, connecting to the Xvnc server running > >> > >>> in the background. In this last scenario the viewer/server use shared > >> > >>> memory for communicating so there is almost no speed penalty. > >> > >>> > >> > >>> Oops, back to the original problem: I run Zmail (a Motif mail > >> > >>> application) and it does not respond to right mouse clicks. > >> > >>> I have programmed Zmail with various pull-down menus hooked to > >> > >>> the right mouse button, but I can't get to them. When I run > >> > >>> Zmail in a normal X session (non-VNC) then I get the right-button > >> > >>> menus without problems. > >> > >>> > >> > >>> It is interesting however, that in the root window in the VNC > >> > >>> session the window manager (twm) DOES get the right mouse button > >> > >>> events because the menu I created for it pops up. > >> > >>> > >> > >>> I have not been able to solve this problem yet. I think there > >> > >>> might be a problem with the mouse button event forwarding from > >> > >>> the Xvnc server. The reason I think the problem is in the server > >> > >>> and not the viewer is that it happens in both the Windows viewer > >> > >>> and the X viewer. > >> > >>> > >> > >>> Thanks > >> > >>> > >> > >>> -- > >> > >>> Freddy Jensen, Sr. Computer Scientist, Adobe Systems Incorporated > >> > >>> 345 Park Avenue, San Jose, CA 95110-2704, USA, Ph: (408) 536-2869 > >> > >>> Email: [EMAIL PROTECTED] > >> > ><mailto:[EMAIL PROTECTED]?Subject=Re:%20Mouse%20right-click%20problem&In-Reply-To=%3C001011105308.ZM10680@voyager%3E>, > >> > > >> > >-- > >> > > > >> > >Regards, Mark. > >> > >--------------------------------------------------------------------- > >> > >To unsubscribe, send a message with the line: unsubscribe vnc-list > >> > >to [EMAIL PROTECTED] > >> > ><mailto:[EMAIL PROTECTED]?Subject=Re:%20Mouse%20right-click%20problem&In-Reply-To=%3C001011105308.ZM10680@voyager%3E> > >> > >See also: http://www.uk.research.att.com/vnc/intouch.html > >> > >--------------------------------------------------------------------- > >> > --------------------------------------------------------------------- > >> > To unsubscribe, send a message with the line: unsubscribe vnc-list > >> > to [EMAIL PROTECTED] > >> > ><mailto:[EMAIL PROTECTED]?Subject=Re:%20Mouse%20right-click%20problem&In-Reply-To=%3C001011105308.ZM10680@voyager%3E> > >> > See also: http://www.uk.research.att.com/vnc/intouch.html > >> > --------------------------------------------------------------------- > >> > > >> > ------------------------------------------------------------------------ > >> > > >> > * *Next message:* Joe Knapka: "Re: Who has VNCView ActiveX?" > >> > <http://www.uk.research.att.com/vnc/archives/2000-10/0200.html> > >> > * *Previous message:* Mark Rainford: "RE: Mouse right-click > >> > problem" > >> > <http://www.uk.research.att.com/vnc/archives/2000-10/0198.html> > >> > * *Messages sorted by:* [ date ] > >> > <http://www.uk.research.att.com/vnc/archives/2000-10/date.html#199> > >> > [ thread ] > >> > <http://www.uk.research.att.com/vnc/archives/2000-10/index.html#199> > >> > [ subject ] > >> > <http://www.uk.research.att.com/vnc/archives/2000-10/subject.html#199> > >> > [ author ] > >> > <http://www.uk.research.att.com/vnc/archives/2000-10/author.html#199> > >> > > >> > > >> > ------------------------------------------------------------------------ > >> > > >> > / This archive was generated by hypermail 2b29 > >> > <http://www.hypermail.org/> : /Wed Nov 01 2000 - 23:50:09 GMT// > >> > > >> > >> > >> > > -- Regards, Mark. --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html ---------------------------------------------------------------------
