ExecuteScriptText

Share icon

Tue, 08/23/2016 - 07:14 am

Hi,

I have a slight problem with the transition to Igor 7. I have a script to import the measured data. As part of the script I call "ExecuteScriptText" to unpack a .7z file. With Igor7 I get the message, that the system could not find the path. Needless to say, that Igor6 and my cmd.exe execute the commandline properly:

ExecuteScriptText "\""+ParseFilePath(5, SpecialDirPath("Igor Pro User Files", 0, 0, 0)+"User Procedures:bin:", "*", 0, 0)+"7z.exe\" e \""+ParseFilePath(5, path+filename+".7z\"", "*", 0, 0)+" -o\""+ParseFilePath(5, path, "*", 0 ,0)+"\" -y"<br />


A resulting path would look like the following string:
"D:\Users\Lars\Documents\Uni (Gö)\Entwicklung\Igor Pro 7 User Files\User Procedures\bin\7z.exe" e "D:\Users\Lars\Desktop\2014-11-24\ShoT_001-C3F6O.7z" -o"D:\Users\Lars\Desktop\2014-11-24\" -y


I'm a bit out of ideas on this one ...


With best regards, Lars
Is the command that is actually executed identical on both IP6 and 7?

I suggest that you try a command that contains onlyascii characters. The command you posted above has an ö in it, and it's possible this is the problem. If so, let us know and we'll take a look.

August 23, 2016 at 07:21 am - Permalink

Quote:
I have a slight problem with the transition to Igor 7.


This appears to be a bug in Igor7. It is passing UTF-8 text to a Windows routine that expects system text encoding (typically Windows-1252).

I will investigate.

August 23, 2016 at 09:34 am - Permalink

I have fixed this. The fix should be available tomorrow (Wednesday, August 24) morning. Choose Help->Igor Pro Nightly Builds to get it.

August 23, 2016 at 12:16 pm - Permalink

I have fixed this. The fix should be available tomorrow (Wednesday, August 24) morning.

Awsome, thanks!

August 24, 2016 at 04:01 am - Permalink