Read the statement by Michael Teeuw here.
Third-Party Module - how to get help?
-
@ember1205 said in Third-Party Module - how to get help?:
Oh, I’m well aware. This sort of stuff is “what I do” every day.
cool…
i can’t explain why it wasn’t shown before… I see it all the time (assuming I don’t have some filter enabled to select just messages for specific modules…)…
oh I did a dummy routine to replace the MM provided one that echos notifications received,
cause the darned clock module sends an annoying notice every second. -
@sdetweil said in Third-Party Module - how to get help?:
cause the darned clock module sends an annoying notice every second.
hasn’t this been resolved with a recent update? If not it should be.
With the update to 2.10.0 I don’t get any notifications by the clock anymore. -
@lavolp3 not different
if (self.config.displaySeconds) if u have seconds displayed on your time, u still get notices
this is the default setting (was on 2.9, is on 2.10)
-
@ember1205 you need to do another git pull…
i found a case where it doesn’t update the image anymore…
-
@sdetweil said in Third-Party Module - how to get help?:
@ember1205 you need to do another git pull…
i found a case where it doesn’t update the image anymore…
Will do.
As an aside… I directly witnessed an odd scenario the other day when I had it refreshing every five minutes… one of the images only loaded the upper half on the screen (the bottom half of the screen had no image and was blank). I could not tell what image it was as I have quite a few in rotation and the frame continued on cleanly from there with the next image.
Is that in any way related to what you found?
-
@ember1205 no… I have seen the slow paint issue myself many times…
electron is having some painting problem… again we are on 3.0.13, no longer supported since way back…
I had tried to get us to 6.0.12 this release, but the test system failed, and they removed this change from the 2.10 release
(but I have seen paint problems on 6.0.12 too)u can try this manually
cd ~/MagicMirror npm install electron@6.0.12 -
@sdetweil said in Third-Party Module - how to get help?:
@ember1205 no… I have seen the slow paint issue myself many times…
electron is having some painting problem… again we are on 3.0.13, no longer supported since way back…
I had tried to get us to 6.0.12 this release, but the test system failed, and they removed this change from the 2.10 release
(but I have seen paint problems on 6.0.12 too)u can try this manually
cd ~/MagicMirror npm install electron@6.0.12What I saw seemed to be different from a “slow paint” issue - it painted the top half and stopped. It sat there for a few seconds and then the image switched to the next one.
While upgrading manually would certainly get me to something newer for Electron, it puts me in the position of not having a “standard install” for future troubleshooting and such. It’s a double-edged sword…
-
@ember1205 said in Third-Party Module - how to get help?:
It’s a double-edged sword…
yep…
What I saw seemed to be different from a “slow paint” issue
yes, interrupted paint… could be same issue, or … (the ‘not quite single threaded’ problem again
got interrupted, never came back) -
@ember1205 said in Third-Party Module - how to get help?:
What I saw seemed to be different from a “slow paint” issue - it painted the top half and stopped. It sat there for a few seconds and then the image switched to the next one.
from our text messages, I think this was caused by the bug u found on image update scheduling…
I have fixed that now (thanks by the way, been looking for it for over a year now) -
@sdetweil said in Third-Party Module - how to get help?:
@ember1205 said in Third-Party Module - how to get help?:
What I saw seemed to be different from a “slow paint” issue - it painted the top half and stopped. It sat there for a few seconds and then the image switched to the next one.
from our text messages, I think this was caused by the bug u found on image update scheduling…
I have fixed that now (thanks by the way, been looking for it for over a year now)I don’t know that I deserve any credit here as I just passed along an observation after you modified your code based on a question I had about whether it was possible to do something. Glad you found and corrected something you had been chasing, though.
