From 0bb003d3d80c6d1a67db5892670950cc88c775d9 Mon Sep 17 00:00:00 2001
From: Edward Shen <code@eddie.sh>
Date: Tue, 19 Feb 2019 09:40:43 -0500
Subject: [PATCH] Apparently the issue in #11 is still present in the newest
 versions of MM.

I've implemented the fix in #11 present by Ax-LED, so hopefully this is
fixed now.

Co-authored-by: Ax-LED <37046881+Ax-LED@users.noreply.github.com>
---
 MMM-pages.js | 16 ++++++++++------
 1 file changed, 10 insertions(+), 6 deletions(-)

diff --git a/MMM-pages.js b/MMM-pages.js
index f30d7e7..9172699 100644
--- a/MMM-pages.js
+++ b/MMM-pages.js
@@ -155,12 +155,16 @@ Module.register('MMM-pages', {
       ));
 
     // Shows all modules meant to be on the current page, after a small delay.
-    setTimeout(() => MM.getModules()
-      .withClass(self.config.modules[self.curPage])
-      .enumerate(module => module.show(
-        self.config.animationTime / 2,
-        { lockString: self.identifier },
-      )), this.config.animationTime / 2);
+    setTimeout(() => {
+      MM.getModules()
+        .withClass(self.config.modules[self.curPage])
+        .enumerate((module) => {
+          module.show(
+            self.config.animationTime / 2,
+            { lockString: self.identifier }
+          );
+        });
+    }, this.config.animationTime / 2);
   },
 
   /**