summaryrefslogtreecommitdiff
path: root/mate-session/gsm-logout-dialog.c
diff options
context:
space:
mode:
authorinfirit <[email protected]>2014-11-04 19:58:45 +0100
committerinfirit <[email protected]>2014-11-04 22:08:50 +0100
commit89dc9f01e88055d61245024d2e414727982c63e4 (patch)
treef659832b4d92e71f531e3c6cccdce3306be8ea49 /mate-session/gsm-logout-dialog.c
parent5c371a408a4b71c718eb331c77edfc114fa4114f (diff)
downloadmate-session-manager-89dc9f01e88055d61245024d2e414727982c63e4.tar.bz2
mate-session-manager-89dc9f01e88055d61245024d2e414727982c63e4.tar.xz
manager: track full details of logout request
When we get a logout request, there are two bits of information that come with the request: 1) Whether or not we should seek confirmation by default from the user before proceeding 2) Whether or not individual applications should be given an opportunity to ask us to seek confirmation from the user before proceeding. We track the latter in a boolean state variable (forceful_logout), but not the former. We already have an enumeration type (GsmManagerLogoutMode) that can be used to track both bits, though. This commit changes the boolean state variable to the enum type, so the whether-we-should-confirmation information is available deeper down in the logout process. Based on gnome-session commit: d7adaa9111d0f42d11225c7e29a7ee1d37d74d2f From: Ray Strode <[email protected]>
Diffstat (limited to 'mate-session/gsm-logout-dialog.c')
0 files changed, 0 insertions, 0 deletions