# Help button in node properties

**URL:** <https://discourse.nodered.org/t/help-button-in-node-properties/73727>\
**Category:** Developing Nodes\
**Tags:** flexdash\
**Created:** [15 January 2023 20:42 UTC](https://discourse.nodered.org/t/help-button-in-node-properties/73727 "2023-01-15T20:42:06Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![kevinGodell](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/kevingodell/32/27040_2.png) [@kevinGodell](https://discourse.nodered.org/u/kevinGodell)\
**Post date:** [16 January 2023 14:01 UTC](https://discourse.nodered.org/t/help-button-in-node-properties/73727/11 "2023-01-16T14:01:19Z")

</div>

> [@tve](#):
>
> For example, after several tries WRT introducing a notification into the flow editor when all nodes have been loaded I have given up. I have now dealt enough with the async loading that I can show that there's no clean work-around. All I can do is shrug my shoulders and add some more hacks.

Do you have another discussion open about this somewhere? I am just curious if it is related to something I recently came across in the editor trying to run code in the `onpaletteadd` function and realizing that `RED.nodes.eachConfig` can never find my config node because it is **too soon to check**. I am still trying to determine if that is a bug or just the expected behavior. Regardless, I have a pretty clean workaround for it by adding `RED.events.on('runtime-state', handleRuntimeState)` in the `onpalleteadd` function. After the first time it detects `obj.state === 'start'`, I remove the event listener.

> [@tve](#):
>
> if (RED.version \< 3.x.x)

Good idea. I will use that technique to **not** include my help button.

---

_[View the full topic](https://discourse.nodered.org/t/help-button-in-node-properties/73727)._