also no longer warping mouse to 0,0 when setting server screen
info. that was causing the mouse to jump if the server screen
had itself as its left or top neighbor (directly or indirectly)
once a screen could be its own neighbor.
include a screen that was already connected under an alias
then that screen wouldn't be disconnected and removed from
the screen list until the screen voluntarily disconnected.
at that time removeConnection() would assert because the
screen name would not be found. now using the canonical
name in the protocol object as well as CServer. this
allows setConfig() to always detect removed screens and
disconnect them.
the address and port to listen on or connect to. changed the
default port and put it in ProtocolTypes.h. the HTTP port is
now no longer opened unless the --http argument is supplied
or the config file includes it.
restarting and daemonizing on unix. daemon sends log messages
to syslog. unix now reads config file from file named on
command line; if no command line arg then uses effective
user's config file and if that's not there it finally tries
/etc/synergy.conf. if there are no screens configured then
one is added for the primary screen. broke some startup
stuff on win32.
also now timing out if X primary screen can't grab the mouse
and keyboard. the server will just give up trying to switch
screens. the grabs will fail is some other app has a grab
and won't release it. note that kdm grabs the keyboard for
the duration that the login window is displayed, effectively
disabling synergy.
of a number). fixed a comment related to what those priority
strings are. added a CLOG_PRINT priority which is never filtered
and suppresses the trace info and the priority level message.
it's intended as a way to output a message through the logger
without getting extra output.
the apps still exit but they do it in a mostly controlled
manner. in particular, the server threads except the one
processing primary screen events will terminate gracefully.
this will be important should the server ever allow HTTP
clients to rewrite the configuration file.
note that X makes it effectively impossible to continue once
the X server disconnects. even if it didn't it would be
difficult for synergy to recover. users will have to add
synergy to the X display manager's startup script if they
expect the server to be restarted. alternatively, we could
add code to fork synergy at startup; the child would do
the normal work while the parent would simply wait for the
child to exit and restart it.
