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>
This commit is contained in:
Edward Shen 2019-02-19 09:40:43 -05:00
parent d2323aa116
commit 0bb003d3d8
Signed by: edward
GPG key ID: 19182661E818369F

View file

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