Notices

I have the same problem, both with OSXvnc 1.6.1 and with the newly released Vine Server 2.0. (OSXvnc changed its name with the latest release.

Some more information:

It's not specifically a CAPS thing. Any character that would require the shift key on a normal keyboard shows up as the un-shifted version. Thus:

• Shift + "a" shows up on the other system as "a"
• CAPS + "a" -> "a"
• Shift + "1" -> "1"
• "@" -> "2" (Note: "@" does not require the shift key on the virtual keyboard. It still shows up as a "2". Similarly, with "!".)

The symbol palette on the virtual keyboard doesn't work. If the symbol in question is a Shifted version of something on a standard keyboard, it shows up as the unshifted version. (e.g., "%" becomes "5".) Otherwise, if it's a Greek letter or the like, nothing happens at all.

One can't input capital letters with the handwriting recognition either.

However, this problem is confined to the on-screen input methods. I hooked up a Freedom bluetooth keyboard using kbdd, and it worked fine. I could input capital letters, symbols, etc.


Looking at the bug reports and release notes for OSXvnc/Vine Server (sourceforge project), it appears there are other keyboard-related issues with this server. There are problems with non-US layouts, for example. I'm not sure whether these are related problems.


Thanks for this wonderful application! It's one of the most useful things I've got on my 770. I haven't had any problems other than this text input issue. I do have one feature request: it would be nice if VNC Viewer had some way to store/bookmark favorite server addresses. An alternative would be for VNC Viewer to process command line arguments; I'd be happy if "vncviewer example.org" launched VNC Viewer and tried to connect.

(To simulate this functionality, I stored my server's domain name as a handwriting shortcut. It does save some typing, though I have to switch input modes.)

Thanks again,

Chris

Thanks for the detailed report.
I am not sure how I can track this issue, as I do not have osx.
I do not have bluetooth keyboard either to check for differences.

If anybody has a linux (or windows) vncserver with simelar problems, please tell me.
Does anybody have a osx server I may access via internet to test?

At the moment my ToDo has the following issues:
19 Nov 06:
CAPS problem with OSXvnc
Command line argument with address
2 Nov 06:
paste from input keyboard does not work.
right and middle mouse click
fullscreen marker in menu wrong if started at fullscreen

23 Oct 06:
Scrolling with - Button and pen

I think I will try to fix some of the bugs within the next two weeks.

Hi all,

I've finally gotten back to working on VNC viewer after taking a break for 6 months or so, and working with Detlef, I have released a new version. It happens to have the same version number as Detlef's latest version, 0.4.1, but there are quite a few changes. While the most recent IT2005 version that I released was 0.3, I actually worked on a 0.3.1 and a 0.3.2 version, and those changes can be found in 0.4.1. Probably the most significant change for most users is the support for command-line options. Use vncviewer.sh --help from xterm for more information. You can pass in both the hostname and password, and there are some other options related to a new lockdown feature. Also, if you don't currently have VNC viewer installed, you will have the option of selecting which menu to use when it is installed.

Thanks to Derek Coleman for his initial port of my 0.3 version to IT2006.

There are several ways to get the latest version of VNC viewer. The easiest way is to get it from the Extras repository. Go to http://maemo.org/maemowiki/Applicati...cdae0be4de7df5 to get the requisite information--you may already have the extras repository in your list of repositories for Application Manager. Plus, by using the repository, it will be very easy to get new versions of VNC viewer when they become available. Alternatively, you can download and install the package directly, at https://garage.maemo.org/frs/downloa....4.1_armel.deb .

Detlef and I also have a new Web site, although there isn't much content. It's at https://garage.maemo.org/projects/vncviewer/ . You can submit bugs from this Web site, download a source package, and browse the source that is checked into SVN. There isn't much content at this Web site, but that will likely change soon.

I've included the changelog since 0.3 below.

vncviewer (0.4.1):
* Reenabled CoRRE as it was a bug in vino (Detlef)
* Some performance improvements especially for 24-bit depth (Detlef)
* Enhanced user interface feedback for fullscreen feature (Aaron, Detlef)

vncviewer (0.4):
* Updated to IT2006 (much of work done by Detlef Schmicker and Derek Coleman)
* Bug fix: Disabled CoRRE encoding, as it does not work, at least with vino server (Detlef)
* Replaced user/password dialog with password dialog

vncviewer (0.3.2):
* Completed feature: Completed lockdown mode by disabling the Home button. Depending on the environment, this also requires a change to maemo_af_desktop. Also, disabled the default behavior for a long back key press, which is to exit the application
* New feature: Added Reconnect button to hardware key lockdown disable password dialog which allows the regular user to force a reconnect
* New feature: Added Admin... button to reconnect dialog which is displayed when unable to connect in lockdown mode. Pressing the Admin... button allows the user to disable lockdown mode if the proper password is entered.
* Bug fix: addressed issue where application did not appear in the task bar (this bug was added in 0.3.1)
* Misc change: Changed hardware key lockdown disable timeout from five to two seconds
* Misc code cleanup

vncviewer (0.3.1):
* New feature: added support for automatically connecting to a network
* New feature: added general command-line argument support--use vncviewer --help for more information
* New feature: added ability to pass hostname and password into vncviewer via the command-line (using the --hostname and --password options, respectively). If --hostname and --password are used and the connection is dropped, vncviewer will attempt to automatically reconnect.
* New feature: added lockdown user interface ability, activated with the --lockdown command-line option. In lockdown mode, the user interface only responds to mouse input and any key activity is ignored. The user interface also automatically goes to full screen and the toolbar is disabled. If a hardware key is held down for five seconds or more, lockdown mode may be disabled. If no lockdown password is specified with the --lockdown-password command-line option, lockdown mode is disabled. If a password is specified, then a dialog is displayed requesting the password. If the connection dies or the client is unable to connect to the server in lockdown mode, a special message box is displayed, and pressing the OK button automatically results in reconnect.
* Misc change: the list of encodings sent is now the same for both local and remote servers. This addresses the slow user interface as a result of using the raw encoding when connecting to a server via an SSH tunnel.
* Bug fix: addressed issue that resulted in a phantom image of the horizontal scroll bar sticking around after disconnecting from a server in full screen mode.

Aaron

Welcome back Aaron. Glad to see you continue work on VNC viewer. I too, plan on getting back to doing some more Maemo development. I hope to see some more great work form you and Detlef soon.

- Derek

hello, i've been having a problem with vncviewer, even after installing the new version as above. when connecting to my ubuntu desktop, the vcnviewer window closes after i input my password. i've tried rebooting, but nothing changed. i can connect to the desktop through my ubuntu laptop with no trouble.

any ideas?

thanks,
-steve

This has come up a number of times in discussions regarding VNC viewer and vino. The problem is with vino, and apparently, the problem has also been fixed. For more information, go to http://www.gossamer-threads.com/list...velopers/13344 and http://physik.de/770/.

AaronL

i already have the physik.de version, and i'm trying to connect to a dapper system, not edgy. are the issues the same?

thanks,
-steve

Most likely. You can download a different version of vino from physik.de/770 that works with the VNC viewer for maemo. The bug is in vino.

Alternatively, you could run vncserver or possibly x11vnc as your VNC server.

AaronL

ok; stupid question:

the new vino is going to be installed on the dapper machine, and not the 770, right?

sorry... thanks for the reply!

-steve

Right. Vino is a VNC server and hosts your desktop, whereas the 770 is being used as a VNC client/viewer that connects to the server.

AaronL