summaryrefslogtreecommitdiff
path: root/changes/4035_add-eip-cancel-button
diff options
context:
space:
mode:
authorkali <kali@katsi>2014-07-27 19:00:37 -0500
committerkali <kali@katsi>2014-08-01 15:40:04 -0500
commit3b469a2c006381ba9e56c1de92be4e87ad67e51b (patch)
treec3f52f9b7f19f1e0f9b176fe935a9e6e31324e2f /changes/4035_add-eip-cancel-button
parent3b02e227cfa48074739eb4f6634a436e65923b61 (diff)
Add cancel button for EIP connection.
Closes: #4035 This falls in the "quick" workaround category. A proper state machine that extends the four basic connection states is hence needed. We have to accomodate design to have a connection-oriented state machine in the backend (I would favor a twisted protocol for this), and a more lightweight one that conducts the gui-level changes (ie, change the actions / buttons / labels accordingly). Since this "cancel" functionality has been long postponed, I chose to do one more ugly hack here, that is, show and hide dance with a button that just calls the bitmask-root to kill the vpn process. It should work well enough until we get to the reorganization needed for a clean process control for eip.
Diffstat (limited to 'changes/4035_add-eip-cancel-button')
-rw-r--r--changes/4035_add-eip-cancel-button1
1 files changed, 1 insertions, 0 deletions
diff --git a/changes/4035_add-eip-cancel-button b/changes/4035_add-eip-cancel-button
new file mode 100644
index 00000000..ea63f8a4
--- /dev/null
+++ b/changes/4035_add-eip-cancel-button
@@ -0,0 +1 @@
+- Add a button for cancelling ongoing EIP connection. Closes: #4035