hostname on each connection. This allows the client to startup
without being able to resolve the server's hostname. It also lets
it handle changes in the server's address, a typical scenario when
the client is a laptop moving between networks.
function. Because synergy doesn't use posix cancellation, it
cannot wake up a thread waiting on a condition variable. So
the wrapper would wake up periodically to test if the thread was
cancelled (according to synergy's cancellation state) then go
back to waiting. Well the condition could be signalled while
we're testing and be lost and we'd never return from the wait.
So now we wake up after a maximum timeout and return to the
caller. The caller must check for this spurious wakeup but all
callers should do this anyway so we're okay there.
an strange deadlock seen on OSX. The CSocketMultiplexer deadlocks
with two threads, one waiting for m_polling to become false and
the other waiting for m_pollable to become true. The weird part
is that they're both false so the first thread should proceed.
It either didn't receive the broadcast when m_polling went to
false or it's not really checking the actual value of that flag.
I can't see how the former is possible and this change fixes the
latter.
modifiers for all keys for testing purposes and forgotton to fix
that. Now choosing required modifiers per key. This fixes
shift+arrow keys suppressing the shift key and, i think, the
option key not working.
was introduced with the change to print system info to the start
of the log. This message was printed before the service installed
the log handler that directs messages to the event log.
the handling of compose key sequences. The key presses were
suppressed but not the corresponding releases, confusing the
clients. It also adds support for generating keysyms via the
compose key if the necessary dead keys or Mode_switch are not
available.
crs23
crs