UpdateEditStructure needs to be runtime accessible

[nasiratif]

Even more sub-app issues!

The stock SDK docs states that UpdateEditStructure can also be called at runtime, albeit in very extreme cases, because that only happens if you run a sub-app built with an older version of the extension. Because DE strips UpdateEditStructure on runtime builds, new properties aren't accessible to that sub-app and a property error is raised if the extension attempts to access it within the sub-app.

[LB--]

I think it also happens if you open an MFA with older edit data, don't do anything that would trigger loading edit data, and then build out to runtime. I'm not sure if newer versions of Fusion load and update all edit datas during build now, when I last tested it was not done and so old edit datas could be included in new builds.

[nasiratif]

I think it also happens if you open an MFA with older edit data, don't do anything that would trigger loading edit data, and then build out to runtime. I'm not sure if newer versions of Fusion load and update all edit datas during build now, when I last tested it was not done and so old edit datas could be included in new builds.

Interesting point. I just tested on build R280.27 and UpdateEditStructure is called instantly right when I open the MFA without opening any frames. So I guess maybe that only happened on MMF2?

[SortaCore]

Hmm, UpdateEditStructure is kinda heavy with all the things it pulls in. But gating it would just make sub-apps inconsistent.
Can't wait for more "mfx so big in darkedif tho 😭😭" comments later when I add this 🙂

[nasiratif]

Hmm, UpdateEditStructure is kinda heavy with all the things it pulls in. But gating it would just make sub-apps inconsistent.
Can't wait for more "mfx so big in darkedif tho 😭😭" comments later when I add this 🙂

This is just the price you pay to using a heavily-abstracted SDK, gotta tell 'em that 😉

[SortaCore]

This is just the price you pay to using a heavily-abstracted SDK, gotta tell 'em that 😉

They don't listen to reason. They listen to arbitrary emotional attachment to sizes, not the relationship of code capabilities and resulting size.
They don't even know you build for size or speed specifically in optimisations.
You start saying "heavily-" and you already lost them. They'd rather have such a poor coding experience that they give up on ext dev for years because it's "too advanced" for them. 😮‍💨