Filemanager parse object fails

AppleScript
#1

This is odd. When run from an applet this script produces a path ending with two colons.

set myPath to path to me
	
	set folderInfo to parse object myPath ¬
		with HFS results
	
	set autoDownloadingFolder to parent_folder_path of folderInfo
-->>"Macintosh HD:Users:edstockly:AppleScript:AutoDownloading x::"

Rewriting it this way worked:

	set folderInfo to parse object myPath ¬
		without HFS results
	
	set autoDownloadingFolder to parent_folder_path of folderInfo
	set autoDownloadingFolder to POSIX file autoDownloadingFolder as alias
-->>"Macintosh HD:Users:edstockly:AppleScript:AutoDownloading x::"

–SD 8.0.1
–Mac OS 11.4

#2

Thanks, I’ll take a look.

#3

I’m seeing this in other contexts now as well. It’s part of my upgrade to Mac OS 11.

The things that have changed are: SD; Mac OS. I think filemanagerlib is still the same.

#4

I think this one is solved. As reported elsewhere, I had two versions of FilemanagerLib installed, one in system one in user.

The one in user was 2.3.4 and that one has this issue.

The one in system is 2.3.5 and there’s no issue with that one.

#5

Ah, that’ll explain it. I knew the problem rang a bell, just not loudly enough.

1 Like
#6

If I’m working on a script that has use script line without a version, and I click paste tell from the library’s dictionary the version number is added to the line. (which is nice)

But if the script has a use script with an previous version you end up with two use script lines with different versions. Shouldn’t it replace the line with the older version?

#7

We decided not to, to draw attention to the potential conflict.