aboutsummaryrefslogtreecommitdiffstats
path: root/vncviewer
diff options
context:
space:
mode:
authorSamuel Mannehed <samuel@cendio.se>2021-10-05 16:28:59 +0200
committerSamuel Mannehed <samuel@cendio.se>2021-10-05 16:28:59 +0200
commit86ffb61a3bf220eb60b9b3cb25e5dd90c2e2b18c (patch)
treee3c054703de69f15571479048c4a6478a748e18f /vncviewer
parent2f661385147e4b0f188ca917fd93ec0fac5b54a5 (diff)
downloadtigervnc-86ffb61a3bf220eb60b9b3cb25e5dd90c2e2b18c.tar.gz
tigervnc-86ffb61a3bf220eb60b9b3cb25e5dd90c2e2b18c.zip
Remove modal property from ServerDialog
Modal windows are meant to be child windows such as menus or popups that are intended to always appear in front of its parent. Modal FLTK windows without a parent seem to behave strangely on macOS. Such windows can appear in front of their modal children windows. When opening OptionsDialog from ServerDialog, it was easy to get to a broken state by then switching focus back to the ServerDialog. This would cause the ServerDialog to appear in front, but not be useable as the options window would still have control of mouse and keyboard. Additionally, modal windows without parents appear in front of other normal applications on macOS. This means that the ServerDialog couldn't be put behind Safari for example. The fact that ServerDialog was a "modal" window was a bit strange, seeing as it doesn't have any parent windows. Removing the modal property from this window causes all the strange-ness to go away.
Diffstat (limited to 'vncviewer')
-rw-r--r--vncviewer/ServerDialog.cxx2
1 files changed, 0 insertions, 2 deletions
diff --git a/vncviewer/ServerDialog.cxx b/vncviewer/ServerDialog.cxx
index ba0386ca..d49ebb8d 100644
--- a/vncviewer/ServerDialog.cxx
+++ b/vncviewer/ServerDialog.cxx
@@ -112,8 +112,6 @@ ServerDialog::ServerDialog()
button->callback(this->handleConnect, this);
callback(this->handleCancel, this);
-
- set_modal();
}