In Flexible Windows I had to use this phrase to stop mysterious line breaks, so I think say__p and say__pc are the only I6 variables you need to handle. But I haven’t look at what’s going on with the timers so I don’t know how you’d handle them in this case. (I think for FW it wasn’t producing crashes, just unwanted linebreaks in the wrong windows.)
[ Fix spurious line breaks from being printed in the main window after running the refreshing activity ]
To safely carry out the (A - activity on value of kind K) activity with (val - K):
(- @push say__p; @push say__pc; CarryOutActivity( {A}, {val} ); @pull say__pc; @pull say__p; -).