Made the Wimp always call the postfilter when returning from Wimp_StartTask,...

Made the Wimp always call the postfilter when returning from Wimp_StartTask, rather than only if the child didn't Wimp_Poll. Also ensured that nothing untowards happens if the filter tries to claim this apparent "null event".

Options/s/!Common

@@ -67,6 +67,8 @@
 	Option	Mode22,			false:LAND:AutoScroll	; cater for low res modes
 	Option	RealDarwin,		false		; use bitmapped darwin font
 	Option	NoDarwin,		true		; don't even alias it.
+        Option  StartTaskPostFilter,    true            ; always call the post filter on exit
+                                                        ; from Wimp_StartTask
 
         END
 

Version

@@ -4,8 +4,8 @@
         GBLS    VString
         GBLS    Date
 
-Version SETA    395
-VString SETS    "3.95"
-Date    SETS    "15 Oct 1997"
+Version SETA    396
+VString SETS    "3.96"
+Date    SETS    "16 Oct 1997"
 
         END

s/Wimp07

@@ -1115,8 +1115,41 @@ returnerror
         WFS     R5
 01
 ;
+      [ StartTaskPostFilter
+        LDR     R14,sender              ; Are we returning from Wimp_StartTask?
+        CMP     R14,#-1
+        BNE     %FT02
+
+; We're returning from Wimp_StartTask and
+; R0 = task handle of child (or 0). Wimps before 3.96
+; would not call the post-filter in this case, but would
+; call it if Wimp_StartTask returned 0 (so the filter
+; would think a null event was happening.) Now, the
+; Toolbox (and probably other filters) relies on the
+; post filter to monitor the current task. If the postfilter
+; doesn't get called here then there is no way of telling
+; that this task has become active. So, we now call the filter
+; with a null event, and ignore any attempt to claim it. (In
+; the past the filter was able to claim the "null" event if
+; Wimp_StartTask returned 0, causing instant death.
+; This is the problem that hit Toolbox 1.33).
+;
+; Hopefully this shouldn't cause any problems, as filters
+; will have had to be able to deal with the dummy "null"
+; event for at least some Wimp_StartTask calls already.
+
+        Push    "R0,R1"
+        MOV     R0,#No_Reason
+        MOV     R1,userblk
+        CallFilter postfilter           ; call the post-poll filter (ignoring
+        Pull    "R0,R1"                 ; R0 return)
+        B       %FT01
+
+02
+      |
         CMP     R0,#max_reason          ; Valid message?
         BHS     %FT01                   ; No then jump,maybe -> *command from Wimp_StartTask
+      ]
 
         Push    "R1"
         MOV     R1,userblk