# \[Announce\] Dashboard Version 2.19.0, 1, 2, 3, 4

**URL:** <https://discourse.nodered.org/t/announce-dashboard-version-2-19-0-1-2-3-4/18502>\
**Category:** Dashboard\
**Created:** [27 November 2019 08:47 UTC](https://discourse.nodered.org/t/announce-dashboard-version-2-19-0-1-2-3-4/18502 "2019-11-27T08:47:20Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![BartButenaers](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bartbutenaers/32/10476_2.png) [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)\
**Post date:** [13 February 2020 07:13 UTC](https://discourse.nodered.org/t/announce-dashboard-version-2-19-0-1-2-3-4/18502/6 "2020-02-13T07:13:59Z")

</div>

> [@dceejay](#):
>
> Add persistantFrontEndValue property to addWidget options so it possible to avoid replay message to be sent when front end reconnect. PR [#558](https://github.com/node-red/node-red-dashboard/pull/558)

Morning @dceejay,  
Perhaps I'm not interpreting this PR correctly, but could it be a solution for another [discussion](https://discourse.nodered.org/t/refresh-ui-node/13921/40) also? As discussed there, we have implemented @hotnipi's workaround to filter replayed messages by throwing away all messages that arrive during the first N milliseconds. But got today [feedback](https://github.com/bartbutenaers/node-red-contrib-ui-contextmenu/issues/9#issuecomment-585573354) that this doesn't work always, since ALL context menu nodes replay their last state after deploy. Which results in messed up floorplans:

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/4/f/4f599b1470d0293326315f8ce7c351f033726a6b.png)

I could try to make increase the filter time, but then the dashboard becomes unresponsive some time after refresh... So if that pull-request fixes this, that would be awesome!

---

_[View the full topic](https://discourse.nodered.org/t/announce-dashboard-version-2-19-0-1-2-3-4/18502)._