Part of the answer is "that's bad design, kate should store the state
and restore it later".
But we will support this kind of behaviour anyway. Need to let the
application reply "no" to the close request. We'll still need a "force
quit" for misbehaving apps.
** Changed in: canonical-devices-system-image
Status: New => Triaged
** Changed in: qtmir (Ubuntu)
Status: New => Triaged
** Changed in: unity8 (Ubuntu)
Status: New => Triaged
** Changed in: canonical-devices-system-image
Importance: Undecided => Medium
** Changed in: canonical-devices-system-image
Importance: Medium => High
** Changed in: qtmir (Ubuntu)
Importance: Undecided => High
** Changed in: unity8 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1671424
Title:
Applications can not interrupt closing them
Status in Canonical System Image:
Triaged
Status in qtmir package in Ubuntu:
Triaged
Status in unity8 package in Ubuntu:
Triaged
Bug description:
Using unity7:
* Open kate
* write something very important in the text area
* Press Alt+F4 because you're not very smart
* Get dialog saying you have unsaved changes
* You can:
* save (which ends in a quit after saving)
* cancel the close
Using unity8
* Open kate
* write something very important in the text area
* Press Alt+F4 because you're not very smart
* You lost your very important text
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1671424/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
