custompanel embed bug

[Peter Wassink]

When you embed a custompanel in the project (which is a great feature)
if you then close the project, the panel will be gone!
That should not happen in my opinion.
embedding should put a copy of the panel into the project.

[Thierry]

I'm tempted to say "it's not a bug, it's a feature", as this works as I would think it should work: the panel is embeded in the project, so it's tied to the project. So if you close the project, the panel should also be closed.
However I'm not opposed to changing the behaviour on this.

I have a question though: let's say you embed a panel into the project (so it creates a copy of the panel in the project), but you modify the panel afterwards.
When you open the project: what should happen? We would have two different panels, how should the software react? Display both panels and let the user choose what to do? Erase the one stored in the project by the "new" one?

[Peter Wassink]

no not erase, any embedded custompanel would simply be a double for as long as the project is open. (you can tell them apart by the color of the panelname)
And if you need to upgrade the embedded panel, simply delete it and embed the updated panel.

And the embedded panel, though potentially being a double while its project is open, would still disapear after closing the project, so its not that you will end up with dozens of the same panel...
its just that
simply embedding a copy is more direct then duplicating the panel first, then renaming it and then embedding it.

[Thierry]

That's fine by me!
I'll add this request in the to-do list