Path behaviour in DIAdem 2019

[Simon_Aldworth]

Hi,

I've just upgrade to 2019 from a much ealier version. I've used the NI supplied script to look for obsolete commands and am now working through the first of my scripts to update it.

It seems that PATHBEHAVIOR is now obsolete and this has led to a problem with setting the variables ScriptReadPath and LayoutReadPath. The default path behaviour after installation is Standard but I need it to be set to Extended so that I don't overwrite ScriptReadPath when I set LayoutReadPath. However, I can't find any way of setting the path behaviour using my script. I cannot guarantee that every user of my script will manually set the path behaviour to Extended so I would prefer to ensure that it is set using code.

Can anyone help?

Thanks, Simon.

[gsklyr]

Maybe set your settings and click settings -> Save as, that will generate a DDD desktop file with your diadem settings saved.  Ask the users of the script to open diadem with that icon.  Not what you wanted exactly but the only workaround I could think of as I don't know a way of changing it or even checking it in script.

[Brad_Turpin]

Hi Simon,

What do you mainly use the ScriptReadPath variable for?  Could you use the CurrentScriptPath variable instead, and just navigate from there relative to the main VBScript file's location?

It does look like the "extended" file variable scheme is only editable through the *.ddd file, which has to be invoked when starting DIAdem.

Brad Turpin

Senior Technical Support Engineer

National Instruments

[Simon_Aldworth]

Hi Brad,

I use it to load .sud files but I think the reasons for using it are historical (dating back to the ****drvuser functions) as we always stored the sud files in the same folder as the vbs files.

Presumably the sud files can be stored anywhere and any path used to access them?

My work around is to have a path variable set to the master folder and then just stick strings on the end for whichever subfolder I want to access at the time.

It's still a shame that some application settings aren't accessible by code anymore. That's a backwards step if so.

Regards, Simon.