sending a sequence number with enter messages. screens use that
sequence number in clipboard grab and data messages. the server
uses the sequence number to order messages across clients. also
changed secondary screens to send clipboard updates on leaving
(or when grab occurs when not active) instead of on a query from
the server. primary effectively does the same. the query
message has been removed.
now but did notice one problem: when powerbook is primary and
num-lock is on the keypad works fine until shift is pressed
(and released); after that the keypad only works while the
shift key is down.
That key only reports press when pressed and released when
caps-lock is activated and only reports release when pressed
and released when caps-lock is deactivated. I don't know of a
way to detect this behavior so it may have to be configured by
the user. The code assumes normal behavior; will have to add
code to set the flag (perhaps from a user configuration).
not detecting a change to clipboard when synergy window isn't
the owner (since there's no event for this; we'll have to
check when we leave the screen i guess). large transfers
don't seem to work.
clipboard owner support (MS windows done, X windows partial)
added key transfer on ms windows
mutex fixes in CClient (had race conditions)
faster debug output in ms windows
changed temporary screen name to "secondary"
network fixes on ms windows (poll returned wrong result)
fixed transparent cursor on ms windows
wait forever). also fixed early return from sleep due to signal.
now forcing client to initialize CThread to ensure global mutex
gets initialized before threads are used.
isn't implemented and modifier masks are ignored. modifier masks
are new; they indicate the modifier key (shift, ctrl, etc) state
at the time of the key event.
stay off on a socket on linux because a connection clearly
doesn't send data as often as possible. will have to implement
a UDP socket to reduce overhead and avoid these delays. wanted
to do that anyway.
crs