[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 152220] Pointless Kate notification on logout
From:       Maciej Pilichowski <bluedzins () wp ! pl>
Date:       2007-12-31 10:31:47
Message-ID: 20071231103147.3729.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=152220         




------- Additional Comments From bluedzins wp pl  2007-12-31 11:31 -------
Maybe first of all some thoughts:
a) it is really a good way to spot a problem, generalize it, and then find a solution \
to general problem b) solution should be universal (see below)

Let's deal with (b) first.

> The user could click on the on-screen display before it disappeared,
> blocking logout/shutdown. 

Bad UI design -- think: handicapped people. 

> I just had an idea - it could be a useful kate feature anyway! On screen
> display just like thunderbird. 

OSD is just a way of displaying data, it is not solution per se, so it would be good \
to leave it out for a while.

> 1[ ] ignore external changes on log out / shut down 
> * reloading the document would be pointless - the user is logging out; kate
> is about to exit 
> * overwriting the document without notifying the user could be potentially
> disastrous 

Ignoring could be disastrous as well. Let's take a look:

app A --> data <-- app B

I cannot tell which app is more important. But you see here Kate is A, thus Kate is \
less important and data should be modified as B likes it.  
> * ignoring the file change modifications is what the check box is for 

And how this design works with modified file in Kate and modified externally at the \
same time (while logging out?).  

I agree with you that it would be nice to have question-free shutdown solution but it \
should be "smart" and error-prone.

I have an idea how to solve it 100% error-prone and with respect to data safety but \
it takes two more reports -- first autobackup feature and second session snapshot on \
shutdown.


[prev in list] [next in list] [prev in thread] [next in thread]