Updates for Version 1.1.3.

FAQ

@@ -12,12 +12,13 @@ Questions
 7.  Why do my CapsLock and NumLock keys act funny?
 8.  Can synergy share the display in addition to the mouse and keyboard?
 9.  Can synergy do drag and drop between computers?
-10. Do AltGr or Mode-Switch work?
+10. Do AltGr or Mode-Switch or ISO_Level3_Shift work?
 11. Why isn't synergy ported to platform XYZ?
 12. My client can't connect.  What's wrong?
 13. Linking fails on Solaris.  What's wrong?
 14. The screen saver never starts.  Why not?
 15. I can't switch screens anymore for no apparent reason.  Why?
+16. I get the error 'Xlib: No protocol specified'.  Why?
 
 Answers
 -------
@@ -126,13 +127,14 @@ Answers
     No.  That's a very cool idea and it'll be explored.  However, it's
     also clearly difficult and may take a long time to implement.
 
-10. Does AltGr/Mode-Switch work?
+10. Does AltGr/Mode-Switch/ISO_Level3_Shift work?
 
     Yes, as of 1.0.12 synergy has full support for AltGr/Mode-switch.
     That includes support for most (all?) European keyboard layouts.
     All systems should be using the same keyboard layout, though, for
     all characters to work.  (Any character missing from a client's
-    layout cannot be generated by synergy.)
+    layout cannot be generated by synergy.)  There is experimental
+    support for ISO_Level3_Shift in 1.1.3.
 
 11. Why isn't synergy ported to platform XYZ?
 
@@ -169,19 +171,13 @@ Answers
 
 15. I can't switch screens anymore for no apparent reason.  Why?
 
-    This sometimes happens but all the causes aren't yet known.  One
-    known cause is if the synergy server in running on Windows
-    95/98/Me and a 16-bit application is in the foreground when the
-    screen saver starts.  Windows fails to notify synergy that the
-    screen saver has started in this situation (which is a bug in
-    Windows, not synergy) and synergy may intercept some keyboard
-    input and divert it to a client when the screen saver is running.
-    As a result, it's possible for the server system to believe a key
-    is pressed when it really isn't.  Typically, it's the return key
-    and simply tapping it will allow synergy to switch screens again.
-    
-    If this problem happens to you, try tapping the enter key to see
-    if that solves the problem.  If not, you can try running with
-    debug logging (--debug DEBUG) and synergy will report exactly why
-    it refuses to switch screens.  If it claims a key is down then
-    try tapping that key and see if that solves the problem.
+    This should not happen with 1.1.3 and up.  Earlier versions of
+    synergy would not allow switching screens when a key was down and
+    sometimes it would believe a key was down when it was not.
+
+16. I get the error 'Xlib: No protocol specified'.  Why?
+
+    You're running synergy without authorization to connect to the
+    X display.  Typically the reason is running synergy as root when
+    logged in as non-root.  Just run synergy as the same user that's
+    logged in.