The Next Generation display numbers

[Jonathan Morton]

>Sure;  my point is the method used for tying ports and displays together. It
>makes use of custom lower-numbered ports significantly more difficult.

I addressed this in ChromiVNC, by writing two very simple routines to 
convert between display and port number (both ways).  I then 
dedicated one input field to the display number, and another to the 
port number.  The two were linked together using the two routines, so 
typing in either one would update the other on the fly.  In addition, 
it remembered which one had last been typed in, and used that to 
determine which value to save in the Preferences.

Fundamentally, it's a user-interface problem, so that's how I addressed it.

-- 
--------------------------------------------------------------
from:     Jonathan "Chromatix" Morton
mail:     chromi "at" cyberspace.org  (not for attachments)
website:  http://www.chromatix.uklinux.net/
geekcode: GCS$/E dpu(!) s:- a21 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$
           V? PS PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r++ y+(*)
tagline:  The key to knowledge is not to rely on people to teach you it.
---------------------------------------------------------------------
To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------