Important notes when updating from Next Design V5.0 to V5.1


Table of Contents

Extended Contents

Please note the following points for this update.

Extensions

V5.1 compatible

Since no APIs were removed or merged in V5.1, extensions developed for V5.0 will generally work without any changes.
However, due to the speed improvements in opening projects, some behavior from the perspective of scripts and extensions will change. In V5.1, the information necessary for display is loaded first, and the remaining model files are loaded in the background.
If you wish to continue using extensions that meet the following conditions in V5.1, please review their contents and take appropriate action as needed.

For details on the changes in V5.1, please refer to the following manual.

IF YOU ARE USING AN API THAT CHANGES BEHAVIOR

In V5.1, the behavior of the following APIs will change. If you are using these APIs, please check if they affect the operation of your extension and revise your processing as needed.

API Changes
IModel.Delete method Models that have a base model for manually loaded model files under them can no longer be deleted (an error will occur).
In V5.0, it was possible to delete the file, but a model file without a parent remained.
IProject.GetModelById method When manually loading a model, if you retrieve a model from an unloaded model file using its ID, it will now return a proxy model instead of null, even if it is not referenced by an already loaded model.
Post-Project Opening Events (onAfterOpen)
Project reload event (onAfterReload)
This now occurs before background loading is complete.
If your event handlers reference the entire project's models, consider moving that processing to the "onAfterAutoLoad" event, which occurs after the loading is complete.
Additional post-load event (onAfterModelUnitLoad) This now also occurs when a model file with manual load settings is loaded via screen operation.

When referring to the library bundled with Next Design itself

If your extension development project does not reference any libraries bundled with Next Design other than the ExtensionPoints development package (*1), the following confirmation is not required.

If you are developing an advanced extension and referencing the same libraries bundled with Next Design in addition to the extension development package, the version of the library referenced at runtime may change due to version upgrades of the bundled libraries.

Please refer to the following manual to verify that your extensions operate correctly.

(*1) Extension development packages: NextDesign.Core, NextDesign.Desktop, NextDesign.Desktop.ExtensionPoints

(Note 2) For details on the libraries included with Next Design V5.1, please contact us through " Technical Support " here.

That is all.