Unpublishing can be tricky: npm Unpublish Policy | npm Docs
But it will definitely be depreciated at some point in the near future.
And the home page needs updating 
It will be done: Update readme: remove "flowforge" · Issue #317 · FlowFuse/node-red-dashboard · GitHub
Ignore! I believe I misread what Julian meant. The SRC readme has already been updated to state "Install the @flowfuse/node-red-dashboard package".
When the flowforge package is depreciated, we will be sure to point to the new package.
I don't suppose that it would be possible to add a link into the Dashboard 2.0 layout panel that would bring the appropriate node into view in the flows would it?
So that you could click a link against one of those inputs and see the node in the flows.
That would really help people better understand and use the link between the flows and the layout panel I think.
You can, of course, edit the node direct from the panel but that doesn't help you find the context of that node in your flow.
1 Like
Agree - great idea. Open an issue please and I will get it scheduled it in.
1 Like
Thanks. Done.
Merged into main - will put this in the next release this week.
5 Likes
We talked in another post about FLEXDASH and some of its features that I like because D1 doesn't have it:
Can we hope that D2 will be able to zoom in the curves?
Can you open an issue on Issues · FlowFuse/node-red-dashboard · GitHub please
I think that is a feature of the charting library used, it is a default behaviour in some charting libraries.
1 Like
it's done
Is this a bug? I have a dropdown selector driven from MQTT (though I don't think that is relevant). I can change the selection in the dropdown by injecting a value from MQTT. However, if I then then open the dashboard on another device then the dropdown does not show the previously selected value. It shows the initial state instead.
With other widgets such as text and switch the current state is correctly shown when a new session is started.
With D1, opening another session on the dashboard shows the previously selected value in the dropdown.
Definitely a bug. Open an issue please 
With D1, if I configure a dropdown node with a label, configured like this
It appears in the dashboard as
However, if I configure a D2 dropdown in the same way
it appears as
If I want a label in front of the dropdown I have to use a separate text node. Is the different layout intentional?
@joepavitt can you comment on this?
Yes - the new design/layout is intentional. This uses the new Material Design framework/layout which is also what Vuetify uses: Select component — Vuetify
Ok, is there any alternative to adding a text node in front of each of my dropdowns?
Currently - no.
I could look at adding a "layout" option to allow for the old option?
1 Like
Probably others should decide how important this is. Perhaps I am unusual in wanting this.
I have another issue with the dropdown, it doesn't do well on small screens. On my phone (Chrome on Android), if I have a two unit wide dropdown there is only enough space for two characters in the text before it truncates. Viewed on the PC it will take 6 characters. The old dashboard manages at least 6 characters even on the phone. The new one appears to waste a lot of space around the box, with the border for example.
2 Likes
