Brandon McCombs said:
That is too specific of a requirement for antything to exist to provide that
level of functionality. You would have to define what "user documentation"
entails and what applications that would include to even have a shot of being
able to implement that.
Forcing open files to be saved when the screensaver starts up is not a good
idea (even if it were possible). I often click save as a kind of fail-safe
checkpoint, then make tentative changes, knowing I can exit without saving
in the event that I screw something up.
Forcing the users to manually save their documents when the screensaver
starts up (even if it were possible) would be counterproductive. This would
prevent the screensaver from logging them off if the user was not there to
actually save his work.
Our policy is that the screensaver simply locks the workstation. If the user
is still around they have the opportunity to unlock and save before logging
off. If not, an administrator does the unlocking or a user power-cycles the
workstation, both of which will cause open files not to be saved.
This may seem harsh, but it is less of a problem than leaving a session
active, and thereby failing to secure sensitive data. Sure, mistakes will be
made, but you cannot make it impossible for mistakes to be made - if you
could, then perhaps you wouldn't need any users ;-). But it is the user that
is accountable for their work - just let them be.
/Al
