Ui-text value delayed initialisation 2 Bugs?

Dashboard
1

A recent release of @flowfuse/node-red-dashboard (Somewhere between 1.22 and 1.29) introduced the possibility of choosing the source of the text node value.

  1. If you set it to use a string (ie the text node content is static), initially nothing is displayed
    image
    image664×195 3.52 KB

Until a message arrives at the node (it need not have a payload), when the value shows up.

image
image510×189 4.96 KB

After the first message, the value is remarkably "sticky", you have to clear the browser cache and/or restart Node-red to see the problem again.

This means that to get static text displayed at startup, you have to connect an inject node set to fire after 0.1 sec to the text node input, effectively making the ability to specify static text redundant.

  1. The default value in this field for a message property is msg.payloads. I believe it should be msg.payload.
    image
2

Could you add a couple of issues to the GitHub repo please please?

If you have time could you check the gauge node and see if it has any similar issues? Though I am not sure how the first one would be seen. If it does then add that to the issue.

They sound like the sort of issues that I should be up to fixing, though I will be otherwise engaged for a couple of weeks.