aboutsummaryrefslogtreecommitdiffstats
path: root/src/modules/objects/KvsObject_dialog.cpp
diff options
context:
space:
mode:
Diffstat (limited to 'src/modules/objects/KvsObject_dialog.cpp')
-rw-r--r--src/modules/objects/KvsObject_dialog.cpp2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/modules/objects/KvsObject_dialog.cpp b/src/modules/objects/KvsObject_dialog.cpp
index f3feb53ff..3752490d9 100644
--- a/src/modules/objects/KvsObject_dialog.cpp
+++ b/src/modules/objects/KvsObject_dialog.cpp
@@ -48,7 +48,7 @@
similar to the widget class, it has only a couple of minor differences.
A dialog is always a top-level widget, but if it has a parent, its default
location is centered on top of the parent. It will also share the parent's windowlist entry.
- !fn; setModal (<boolean>)
+ !fn; setModal (<boolean>)
If you call $setModal(1) then the dialog will have non-blocking modal behaviour:
it will appear above its parent widget and block its input until it's closed.
@functions: