4 Commits

Author	SHA1	Message	Date
crs	4bf0836eae	Synergy no longer tries to suppress the screen saver once it starts. ... It was doing that already if started through synergy but not if started by something outside of synergy. In particular, if you use `xscreensaver-command --activate' synergy used to send fake mouse motion events every 5 seconds to deactivate it. That's unlikely to be what the user wanted, especially if the locking is enabled since it would force the password dialog to appear. As before, it's recommended that client screens not use locking because xscreensaver will not deactivate without getting a password even if we make the request through a programmatic interface. Presumably that's for security reasons but it makes life harder for synergy.	2003-01-11 15:16:41 +00:00
crs	52d8edb747	Fixed bug in detecting screen saver activation. Was using || instead ... of && in conditional.	2002-11-05 19:23:05 +00:00
crs	f6c3a9453b	added copyright to top of each file.	2002-08-02 19:57:46 +00:00
crs	fee4095624	Reorganized source tree. Moved client.cpp into cmd/synergy as ... synergy.cpp and server.cpp into cmd/synergyd as synergyd.cpp. Moved and renamed related files. Moved remaining source files into lib/.... Modified and added makefiles as appropriate. Result is that library files are under lib with each library in its own directory and program files are under cmd with each command in its own directory.	2002-07-30 16:52:46 +00:00

Renamed from platform/CXWindowsScreenSaver.h (Browse further)