#DOCUMENTATION by cg
authorClaus Gittinger <cg@exept.de>
Wed, 19 Oct 2016 13:12:58 +0200
changeset 3764 a76c6c4cd637
parent 3763 72a6db06eee5
child 3765 53f3e400ffce
#DOCUMENTATION by cg class: ApplicationModel comment/format in: #showActiveHelp:for:
ApplicationModel.st
--- a/ApplicationModel.st	Fri Oct 14 12:57:53 2016 +0200
+++ b/ApplicationModel.st	Wed Oct 19 13:12:58 2016 +0200
@@ -2392,14 +2392,14 @@
      some active help bubble; if true is returned, it will assume that the
      help text has been already displayed and will not do any further actions.
      Here, we accept the help text, and push an event into out own input
-     queue, so that the help text will be displayed asyncronously by myself,
+     queue, so that the help text will be displayed asynchronously by myself,
      vis the #showHelp:for: method.
      This can be redefined in concrete classes to handle active help differently."
 
     |wg mySensor|
 
     self showingHelp ifFalse: [
-	^ true
+        ^ true
     ].
 
 "/    masterApplication notNil ifTrue:[
@@ -2414,14 +2414,14 @@
     "/  instead of occurring in the activeHelp context).
 
     (wg := self windowGroup) notNil ifTrue:[
-	mySensor := wg sensor.
-	mySensor notNil ifTrue:[
-	    mySensor flushEventsFor:self withType:#showHelp:for:.
-	    mySensor
-		pushUserEvent:#showHelp:for: for:self
-		withArguments:(Array with:aHelpText with:view).
-	    ^ true
-	]
+        mySensor := wg sensor.
+        mySensor notNil ifTrue:[
+            mySensor flushEventsFor:self withType:#showHelp:for:.
+            mySensor
+                pushUserEvent:#showHelp:for: for:self
+                withArguments:(Array with:aHelpText with:view).
+            ^ true
+        ]
     ].
 
     "/ mhmh - can this happen ?