Revision 4c49986e
Added by Leszek Koltunski over 2 years ago
src/main/java/org/distorted/tutorials/TutorialActivity.java | ||
---|---|---|
31 | 31 |
import com.google.firebase.analytics.FirebaseAnalytics; |
32 | 32 |
|
33 | 33 |
import org.distorted.dialogs.RubikDialogError; |
34 |
import org.distorted.helpers.BlockController; |
|
34 | 35 |
import org.distorted.helpers.TwistyActivity; |
35 | 36 |
import org.distorted.helpers.TwistyPreRender; |
36 | 37 |
import org.distorted.library.main.DistortedLibrary; |
... | ... | |
188 | 189 |
if( mWebView!=null ) mWebView.onPause(); |
189 | 190 |
|
190 | 191 |
DistortedLibrary.onPause(1); |
192 |
BlockController.onPause(); |
|
191 | 193 |
} |
192 | 194 |
|
193 | 195 |
/////////////////////////////////////////////////////////////////////////////////////////////////// |
... | ... | |
197 | 199 |
{ |
198 | 200 |
super.onResume(); |
199 | 201 |
DistortedLibrary.onResume(1); |
202 |
BlockController.onResume(); |
|
200 | 203 |
TutorialSurfaceView view = findViewById(R.id.tutorialSurfaceView); |
201 | 204 |
view.onResume(); |
202 | 205 |
view.initialize(); |
Also available in: Unified diff
1) add missing call to BlockController.onPause() / onResume() to the Tutorial activity
2) rearrange BlockController's error reporting to make the case where the MessageSender thread has died separate
3) in such case, resurrect the thread
4) simplify and harden the EffectMessageSender