Posts made by MMRIZE

@MZ-BER
I was the original author @eouia, that module was built for my own purpose.
Nowadays, I changed my car to Tesla, so I couldn’t maintain that module anymore.
It’s nice to hear @MZ-BER keep the module advanced. I’ll leave the comment on my repository for a visitor who needs Volvo module to use yours.

@tanvir586
Usually not possible. Unless your widget has that kind of feature (size adjust), it couldn’t.

@sifuhall
If your os can handle nodejs, electron and chromium, it could be.
But some modules or features might not be compatible with yours.
Especially sever mode, nodejswould be only the issue.

@arynio

https://github.com/MichMich/MagicMirror/blob/26a76f80d63e5c9746b6db712d6901219f8b6b93/js/main.js#L97-L99

if (module !== sender && (!sendTo || module === sendTo)) {
  module.notificationReceived(notification, payload, sender);
}

module.notifcationReceived() doesn’t work when the recipient module and the sending module are the same.
A module cannot hear its voice.

If you want to use a chained shell commands with delay, make .sh file and execute it.

@arynio
I haven’t tested. But as far as I know, a notification from the module itself would not be heard by itself to prevent infinite loop possibility.

@gekberlin
RelativeTime would be auto-scaled by remain period to target time from now on. So “tomorrow” is displayed as “in X hours” because after X hours the tomorrow will begin. “In 10 days” means exactly “in 10days and a few hours”
So it is not so desirable to display exact time, especially fullday events.
Use dateFormat or dateTimeFormat. See the localization part also.

RelativeTime itself is more useful when you use it to display near events in 24 hours.

@cfenner
It doesn’t work on multi-instances. If you run two fronts ui at the same time, the error will happens.
How to overcome? Well, there be almost no solution for that.
Maybe you can modify node_helper.js not to execute one more instance from another front but I’m not sure that is what you really want.

@night_pr0
Cheers.
Ref. MMM-WeatherBackground, it is not video player but wallpaper something. Anyway you can get an idea.

@bhaules

Just memo;
It seems Indexing 50 photos took around 3~4 seconds. (It is too slower than I expect) 5000 photos will take 3000~4000 sec, = around 50 ~ 60minutes.
But your scanInterval is 10 minutes. It might be the reason? Before finishing the previous scanning cycle, a new cycle might begin.

As I mentioned earlier on github, scanning 5thousands photos every 10 minutes to show random 5 pictures in that 10 minutes, seems not so much efficient.

@sultan-y
Which position did you put the module into? set the position fullscreen_below.