DB 2 - Latest update question and layout editor feedback

Hi

Couple of things:

1- Latest DB 2 update:

I have updated Dashboard 2, and this is how the properties panels now looks:

Are the tab names supposed to look like that? This doesn't seem right to me. I was messing about with themes before the update, so might have deleted something I shouldn't have... If this is how it should be, I think a slightly more intuitive naming would be advisable... Either way, it would be good to know... Thanks very much in advance!

2- Working with DB2 Layout editor

It is surprisingly easy to get out of sync using the very useful and neat layout editor. If something is added or changed in a flow, but not deployed, and changes are then made using layout editor, saving the changes in layout editor will only deploy its changes. Nodered will immediately throw a sync error notification, which then leads to a review of changes and merge. That bit can be very confusing, and lead to loss of work.

I would suggest to include a check for pending changes when the layout editor is opened and a prompt to deploy unsaved changes before proceeding, with an option to ignore for the super pros or cancel and return to the canvas and decide what to do for the less gifted among us. Just my 2 pennies...

Have a good weekend!

There is an open issue for your point 1, apparently it is proving difficult for the developers to replicate. It is not clear under what circumstances it happens. Please add a comment to the issue describing your setup.

I've just figured it out! the NLS function for i18n was moved to Global scope in commit and it competes with ui-templates implementation.

PR incoming

Fixed in Move NLS function to inside of IIFE by Steve-Mcl · Pull Request #1757 · FlowFuse/node-red-dashboard · GitHub

We will get a new release out soon

Excellent. Well diagnosed. Did it only happen if the flow included ui-templates?

I don't use ui-templates if this helps...

Great, thanks a lot!

Thank you very much!

Tbh, I didn't revert to test how or why Colin. I just noticed the function had been moved outside of it's iife and it all made sense. And the fix works!