Relative and absolute path to adopded Parts and assemblies

[TIMOHART]

Hello ,

Adopted parts will be having a relative path in the adopted file such as :

< %%category("Inventor") > _
 Parameter Rule factoryFileDirectory As String = "..\Parts\Cooler"

wheras the adopted Ilogic assembly has a absolute path such as :

< %%category("Inventor") > _
 Rule AssemblyFileDirectory As String = "G:\Inventor\19_ETO\ETO_Entwicklung\ETO_M2013\Parts\PumpConfig\MD80-260_Configurator"

trying to change the absolute path in a relative path was leading to the fact that ETO did not find the assembly .

< %%category("Inventor") > _
Rule AssemblyFileDirectory As String = "..\Parts\PumpConfig\MD80-260_Configurator"

Is this a known behaviour ?

following editing works but is not the right way.

I actually don't know how to do it differently .

< %%category("Inventor") > _

Rule AssemblyFileDirectory AsString = iv_ProjectWorkspace() + "\Parts\PumpConfig\MD150-360-Ahead_Configurator"

What do I need to do with the editable IKS file to overwrite the absolute Path ?

Thank you / Regards

Timo

[ebachrach · Accepted solution]

Hi,

The use of projectlocation(), iv_projectworkspace, identifying the path based on the design library location using LibraryLocation(designLibrary(designName))  are all reasonable parts of a contsruct for ensuring the path are perfectly reasonable. 

So I might use something like this:  AssemblyFileDirectory = iv_pathCombine(LibraryLocation(designLibrary(designName)), myinventorpartfilesdirectory)

I'm not trying to explain why adoption process hardcodes the path.  It hasn't really mattered in my projects because the iLogicAssemblies and their constituent parts are often kept in some other location anyway, so there really hasn't been a reasonable initial assumption about path. 

Elly