search

pixelit-project / node-red-contrib-pixelit

Node-RED nodes to control the Pixel It easily and comfortably.
https://github.com/o0shojo0o/PixelIt/discussions
MIT License
5 stars 4 forks source link

Scrolling does not work when set to "on" #3

Closed o0shojo0o closed 3 years ago

o0shojo0o commented 3 years ago

Hi, I updated to 0.3.7. Brightness and sleep works fine again, scrolling works wenn set to "auto". Thanks for fixing it! Scrolling does not work when set to "on", it displays a static text then. I am fine with the auto setting :)

btw. the latest version does not show up in the node-red palette, I updated with npm install.

Originally posted by @hamster65 in https://github.com/o0shojo0o/node-red-contrib-pixelit/issues/2#issuecomment-814636922

o0shojo0o commented 3 years ago

Fixed in v0.3.8 :)

hamster65 commented 3 years ago

Nice, thanks! Scrolling with "on" works. I found another bug with automatic scrolling: When I send "WINDBÖEN", the last 2 colomns of the last character do not fit (normal text size), so it should auto-scroll, but it doesn't. Sometimes, it displays a static text, but sometimes it shows just random pixels. When it fades to the next screen, the text is readable again during the fade.

o0shojo0o commented 3 years ago

When I send "WINDBÖEN", the last 2 colomns of the last character do not fit

Yes, unfortunately the Pixelit can't calculate that cleanly, I don't have a solution for that, because the letters are not all the same width.

Sometimes, it displays a static text, but sometimes it shows just random pixels. When it fades to the next screen, the text is readable again during the fade.

This behavior can not be produced by these nodes, this indicates malfunctions in the power supply or wiring.

hamster65 commented 3 years ago

Issues with wiring or power supply should give flickering and "colorfull" pixels. But here it only happens with scrolling set to auto, brightness does not influence it and all pixels are in the exact color of the text.

I noticed I had position x=7, y=1 and center=on set in the text node. I set this to zero and disabled and the problem was gone. Then I set it back to reproduce it and it is still gone... Odd.