search

CATIA-Systems / FMIKit-Simulink

Import and export Functional Mock-up Units with Simulink
Other
157 stars 51 forks source link

Rename Actual Unzip Directory when Renaming in GUI #230

Closed Marvin-TMG closed 3 years ago

Marvin-TMG commented 3 years ago

When the unzip directory is renamed in the GUI, the source folder should be renamed as well to avoid accumulating ghost folders.

Steps to reproduce:

Matlab command window output:

Compiling S-function sfun_TS050_Internal_Chassis_Road Failed to compile S-function C:\WORK\Git\DriveabilityModelClean\Simulink\TS050_Internal_Chassis_Road_Renamed\sources\all_TS050_Internal_Chassis_Road.c not found; check that you are in the correct current folder, and check the spelling of 'C:\WORK\Git\DriveabilityModelClean\Simulink\TS050_Internal_Chassis_Road_Renamed\sources\all_TS050_Internal_Chassis_Road.c'. Compiling S-function sfun_TS050_Internal_Chassis_Road Building with 'Microsoft Visual C++ 2017 (C)'. MEX completed successfully. Compiling S-function sfun_TS050_Internal_Chassis_Road Failed to compile S-function C:\WORK\Git\DriveabilityModelClean\Simulink\TS050_Internal_Chassis_Road_Renamed\sources\all_TS050_Internal_Chassis_Road.c not found; check that you are in the correct current folder, and check the spelling of 'C:\WORK\Git\DriveabilityModelClean\Simulink\TS050_Internal_Chassis_Road_Renamed\sources\all_TS050_Internal_Chassis_Road.c'.

The source code paths are also not renamed in the build settings, instead new paths are created, accumulating ghost paths: "C:\WORK\Git\DriveabilityModelClean\Simulink\TS050_Internal_Chassis_Road\sources\all_TS050_Internal_Chassis_Road.c" "C:\WORK\Git\DriveabilityModelClean\Simulink\TS050_Internal_Chassis_Road_Renamed\sources\all_TS050_Internal_Chassis_Road.c"

t-sommer commented 3 years ago

What is the use case for renaming the unzip directory after the FMU has been imported?

Marvin-TMG commented 3 years ago

The usecase is to load a new FMU within the existing block and assign it a different path. The old previous folder and file references will not be disposed in that case.

t-sommer commented 3 years ago

The re-load is designed to import a new version of the same FMU (with minimal changes), so the start values etc. can be reused. To import a new FMU you should delete the block and create a new one.