On Fri, Jan 8, 2010 at 11:50 AM, Nedko Arnaudov <nedko(a)arnaudov.name> wrote:
Chris Cannam <cannam(a)all-day-breakfast.com>
writes:
OK... That sounds rather hazardous to me. To
lose all of one's data
instead of saving it, after a potentially long session's work, because
of a check box incorrectly checked when starting the application,
surely wouldn't please many users?
And you are suggesting what?
Uh, I think you've lost me a bit, Nedko. What do I appear to be suggesting?
I'm just saying that it might not be such a good idea for a session
manager to kill applications instead of saving them, when asked to
save. Especially if that decision is based on user input that
happened a long time ago (so that the user may have done a lot of work
since making their mistake, but before discovering it was a mistake).
Since none of my applications have any support for any sort of session
manager yet, it's hardly surprising that I might be interested in
thinking about how they might behave if someone tried to use them with
one.
Chris