Save, Save as, and Export confusion

[mtarenskeen]

Ctrlr has many different ways to save, save as, or export panels and Ctrlr state.

It's not quite quite clear to me what they all do. Even worse: It is dangerous! The program keeps warning me I need to "save" but more than once I have lost all my work when creating a new panel If I do.

What sometimes happen is that I export my panel compressed including resources (buttons, fonts, grapics etc.).
I click save, because I think "save" = "safe".

The bpanelz file is overwritten but: it does NOT contain the resources. It reloads them from somewhere.
Then I copy (using cloud, or usb stcik) the bpanelz file to test it on my other computer (testing Windows vs Linux).
That's when I find out all custtom buttons, fonts and graphics are gone and lost??

To prevent making such mistakes I must renember the unintuitive CtrlrX rule: SAVE IS NOT SAFE

That can't be how it is meanst to be.
Maybe I am misunderstanding the whole save / save as / export thing in Ctrlr or I am doing something wrong?

[damiensellier]

Maybe you lost your work because you exported the instance then saved it but the path were pointing to the original .panel file It never happened to me and I mainly use save, save as... , and export as a restricted instance only when my project is already baked and needs to be tested as vst for exemple.

I don't know what should I rename those with, let me know if you have a suggestion that would be easier to understand for most of the users. Thanks