Save Global Variable

[[Articy] Nico Probst]

Ah now i understand!
While i don't think i changed anything in particular related to that i do use the same callback to turn the Database back into edit mode.
The problem with those callbacks unfortunately is, that the order in which they are called is random. It is therefor very much possible that it worked by accident this whole time.

I will investigate that issue and see what event would be correct to reset the database without interfering with any user code.

I get back to you as soon as i got more information.

Best regards

Nico

[Zeldarck]

Oh ok thank you, like I said in edit, when it's compile on my android I don't have the problem, but if it can work in edit mode it's better

Thank, waiting your investigate

[Zeldarck]

It's relative to save so I post here. I wanna to save the status of all object with a certain feature, to get all of them, I do

Code: Select all

List<IObjectWithFeatureDisplayCondition> listDisplayCondition = ArticyDatabase.GetAllOfType<IObjectWithFeatureDisplayCondition>();

But since IObjectWithFeatureDisplayCondition I find any way to save the technical name to be able to load the data.

Have you any idea? I have many template with that feature, I prefer to avoid to make a loop for each of them :/

thank you

[[Articy] Nico Probst]

Not sure i understand you correctly, you want to get the technical name of those objects? Remember that every object with such an IObjectWith interface must be an ArticyObject, which itself has the TechnicalName property.

Code: Select all

foreach(var feature in listDisplayCondition)
{
   var obj = feature as ArticyObject;
   SaveTechnicalName(obj.TechnicalName);
   SaveDisplayCondition(feature->GetDisplayConditionFeature());
}

[Zeldarck]

Oh ok, I though IObjectWithFeatureDisplayCondition was different than an ArticyObject

Thank you !

[[Articy] Nico Probst]

Glad that worked for you!

Back to your save issue:
It was again an issue with how unity reports play mode and transition of play mode. I used the improper way and while your OnApplicationQuit is called, the flag was already showing false, which made the GlobalVariables to return their editor values instead of their still valid runtime values.
I fixed that and some other cleanup issues regarding those events and now you should have access to the correct Global Variables values inside OnApplicationQuit.

Now i don't want to release that version to everyone with those changes without further testing, but i also don't want you to wait too long. So if you feel comfortable using a pre-release i built a version with that fix(and some other changes) and you can test for yourself if my changes fixed the problem for you. But keep in mind its a pre-release, so make a backup if necessary and you probably don't want to ship your project until you can use the release version of the plugin.

You can find this pre-release here, or you can wait until i fixed some remaining issues and managed to test those changes further.

Best regards

Nico

[Zeldarck]

Oh really nice job. I have finish the upgrade of my old function, so I will take the version when it will be release

[[Articy] Nico Probst]

Hi Zeldarck,

the new release should allow you to access the global variables even inside OnApplicationQuit.

Thank you again for reporting it!

Best regards

Nico