checkpoint.

notes

@@ -7,6 +7,17 @@ hangup if invalid
 query info			-->		
 					<--		info (size)
 
+---
+enable heartbeat disconnection or remove heartbeat sending in client
+  should either ship with it fully enabled or fully disabled
+  possibly make it part of startup negotiation
+
+---
+sometimes jumping too far into secondary screen
+  probably bogus delta (adding in center pixel coords into delta?)
+  this is with an X primary and secondary
+    don't know which matters but probably X primary
+
 ---
 use automake
 use doxygen
@@ -93,14 +104,6 @@ bug with half-duplex keys
   now grace starts server and is locked to screen
   grace should ignore half duplex keys when seeing if locked to screen
 
----
-must send up key events when leaving screen for keys still down
-  some key combos get eaten and the key ups aren't sent
-  e.g. ctrl+alt+del on win2k to grace
-    mouse is forced back to to win2k
-    ctrl and alt up not sent to grace
-    grace thinks ctrl and alt are down 'til user physically press/releases them
-
 ---
 bug in updating screens
   saw a goofy set of screens after update
@@ -123,10 +126,17 @@ Xsetup file may have to kill previous synergy
 not handling international characters
 
 ---
-screen saver won't lock screen if on secondary screen
-  because synergy has mouse/keyboard grabbed
-  synergy will immediately release grabs when screen saver activates
-    but looks like xscreensaver wont map window until it grabs
+xscreensaver won't start if pointer on secondary screen
+  unless using MIT or SGI screen saver extensions
+  otherwise it cannot know when to stop the screen saver
+    cos it can't grab mouse and keyboard
+---
+all screensavers hidden when showing win32 screensaver lock window
+  win32 kills the screen saver and shows the lock window
+  synergy thinks the screen saver is dead (cos the process is)
+    deactivates secondary screen screen savers
+  user is constrained to locked display, though
+  also, we don't detect screen saver restarting if user doesn't unlock screen
 
 ---
 not distinguishing between caps lock and shift lock
@@ -142,12 +152,7 @@ not distinguishing between caps lock and shift lock
 currently sending all clipboards to all clients
   some clients may not need all clipboards
   add filtering mechanism
-
----
-sometimes jumping too far into secondary screen
-  probably bogus delta (adding in center pixel coords into delta?)
-  this is with an X primary and secondary
-    don't know which matters but probably X primary
+    setup is probably part of clipboard (format) negotiation
 
 ---
 not handling large motif selections
@@ -167,16 +172,6 @@ inconsistencies
     should use pointers for any in/out parameter
       but using references in some places
 
----
-win32 hook DLL sometimes not unloaded when server is killed?
-  will get assertion on restart as if DLL was still loaded.
-  can tell because all DLL copies share data segment.
-  should prevent multiple copies from loading (or initializing)
-    replace asserts with (multithread locked) check of variables
-    return 0 if busy
-    server must handle failure
-  try to figure out why it's not unloading
-
 ---
 avoid fullscreen transparent window on win32
   using CBT hook to discard activation/focus messages
@@ -200,7 +195,7 @@ keyboard hook problems (win32)
     thinks the key is always down.
 
 ---
-try to determine keyboard quirks automatically
+try to determine X11 keyboard quirks automatically
   in particular, set the half-duplex flags
   maybe KBD extension will help determine this
 
@@ -219,6 +214,9 @@ adjust thread priorities on win32
       haven't tried real-time priority
   a very high priority on client fixes delay when typeing into console
   is it the output console causing the slowness?
+  mouse motion compression seems to handle slow dragging on grace
+    pretty sure nothing else was wrong on grace
+    maybe same problem and solution on win32
 
 ---
 results:
@@ -371,11 +369,6 @@ send all toggle states instead of (individual) toggle ups/downs (gspencer)
   and turn it off on the master (and all other clients) too, but I think
   that's probably too complicated to implement.
 
-dragging windows is too slow
-  grace (as client) exhibits this
-    dunno if it happens with audrey2 as the client
-  liz says her windows laptop does it too
-
 double clicking NT binaries fails (liz)
   add note to README or use separate binaries for services.  client
   would also need a dialog to query options.  server would probably
@@ -396,6 +389,24 @@ non-functional on ctrl+alt+del screen in win2k (kurt)
   i suppose it must be when win2k is the client.  mouse input wasn't
   working.  keyboard probably didn't work either.
 
+gspencer:
+  OK, I've narrowed it down a little -- it seems to happen if you have any
+  key down (I tried the shift key and the letter 's' key) when you cross
+  over from master to client, which would make me suspect the "capture"
+  code, since if you have a key down you aren't supposed to be able to
+  cross over...
+
+
+== fixed? ===
+dragging windows is too slow
+  grace (as client) exhibits this
+    dunno if it happens with audrey2 as the client
+  liz says her windows laptop does it too
+  also closing/iconifying has a delay
+  dragging multiple files also sluggish
+
+liz seems to still be seeing sluggish cursor updates
+
 ---
 automake stuff
   rebuild: