Open vanvught opened 3 years ago
Hey Arjan, I've definitely seen this one with linux_e131 firmware, it happened because retrieved file was empty, and not seen elsewhere yet... What is supposed to be in "Display Udf" ?
Hey Arjan, I don't know about the "Display Udf" very well, is returning
.... dmx_direction: 0}}
In the .txt config files, this is string 'input' or 'output' , so this error is happening because I was not expecting 0 or 1....
Did it handle gracefully in the ui and show 0 / 1? I expect it showed "output"
I am simply matching any 'direction' in the attribute name as a switch... https://github.com/hippyau/rnc/blob/11ecd20fe2814a11334f357a109a67534e3093ab/lib/confignodescreen.dart#L202 ... but is expecting a string value, should I handle this and the attribute will always be integer for 'dmx_direction' in this file?
Hi Hip,
The user can define their own display format -> https://www.orangepi-dmx.org/orange-pi/displays/user-defined-format
Ahh, thanks that totally makes sense now :-)
Okay, I can support this.
On Thu, 30 Sep 2021, 05:34 Arjan, @.***> wrote:
Hi Hip,
The user can define their own display format -> https://www.orangepi-dmx.org/orange-pi/displays/user-defined-format
[image: Schermafbeelding 2021-09-29 om 21 31 50] https://user-images.githubusercontent.com/4319913/135336275-5ab8045c-409c-48ab-9da6-9ef4808373c0.png
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/hippyau/rnc/issues/4#issuecomment-930481758, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIWBBRKXD6JWCEMFSK2ACGLUENS25ANCNFSM5E53UNZA .
Hi Hip, getting this error when
DISPLAY_UDF
is defined in the firmware.