On Thu, Aug 23, 2001 at 04:29:47PM -0700, SI Reasoning wrote:
> I use Mandrake's vncviewer and Xvnc since they compile to i586 and
> include tight encoding. I also use Tridiavnc's vncviewer (named
> runvncviewer) since Mandrake's vncviewer only works on command line
> (Mandrake's X vncviewer does not hide the password, and doesn't work
> anyway.) I then use Redhats vncserver script with support for
> /etc/sysconfig/vncservers (I was so happy to discover this!)
(I feel compelled to point out that the Red Hat Linux VNC RPMs do all
of this [the password thing is an Xaw bug which I fixed] except for
the i586/i386 thing: vncviewer is largely I/O-bound so I don't expect
it would make a noticeable difference.)
> If I start off in full screen mode - no keyboard
> If I start off in regular mode and switch to full
> screen, then I have keyboard up until something on my
> (nonvnc) desktop pops up, or I click a key binding
> that is picked up by the (nonvnc) desktop (such as
> {alt + F2} in KDE).
I've also seen the bug, which is why I'm asking you questions about
your environment. :-)
> I do not know a way to bring the keyboard back into
> vnc. If there was a clickable script that was on the
> vnc host's desktop, that would be a way around it. I
> can't recall off hand if I have the same problems on
> windows desktops but I suspect I do.
I would be very interested to know. I suspect not, if Const's
assessment is correct.
Tim.
*/
[demime 0.97b removed an attachment of type application/pgp-signature]
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
