Applescript conflict with the iTunes constants 'error' and 'duplicate'

Try using:

set tCloudStatus to aTrack's cloud status as string

(142604)

Have you tried |duplicate| and |error|?

Those «constant ****kUnk» things are the raw codes for the application constants. These constants are (usually) shown in the Script Editor as a convenience, but for comparisons and use outside of the application tell statement, you should coerce them to text/string as first posted by Neil.

Doing it the long way as in your example it would be something like:

if (aTrack's cloud status as text) is equal to "error" then
--

Hello

Terminology conflict is one of the most annoying and the ugliest things in AppleScript language.

Obviously they have never tested those AppleScript terminologies of iTunes in question to work in real script. I'd recommend your sending bug report to Apple on this matter.

Regards,

H

I suggested these as I was writing some AppleScript/Objective-C the other day where the word error was part of a method invocation, and AppleScript threw a fit until I put the word error in its corral. Yours, in retrospect, is a different issue, as Hiroto has pointed out.

It works fine on my machine running Yosemite - what kind of result do you get?

tell application "iTunes"
  set aTrack to cloud status of current track --> currently playing track
  log class of aTrack --> constant
  set aTrack to aTrack as text
  log class of aTrack --> text
end tell
if aTrack is "unknown" then beep -- status usable outside tell statement

Ah. Yes, that does seem to be broken.

In that case, you'll just need to beat on it the hard way (at least until it gets fixed):

# iTunes 'cloud status' constants:
property kPurchased : «constant ****kPur»
property kMatched : «constant ****kMat»
property kUploaded : «constant ****kUpl»
property kIneligible : «constant ****kRej»
property kRemoved : «constant ****kRem»
property kError : «constant ****kErr»
property kDuplicate : «constant ****kDup»
property kSubscription : «constant ****kSub»
property kNotAvailable : «constant ****kRev»
property kNotUploaded : «constant ****kUpP»
property kUnknown : «constant ****kUnk»

tell application "iTunes"
  set aTrack to current track -- current track
  set status to aTrack's cloud status
  if status = kPurchased then
    set tCloudStatus to "purchased"
  else if status = kMatched then
    set tCloudStatus to "matched"
  else if status = kUploaded then
    set tCloudStatus to "uploaded"
  else if status = kIneligible then
    set tCloudStatus to "ineligible"
  else if status = kRemoved then
    set tCloudStatus to "removed"
  else if status = kDuplicate then
    set tCloudStatus to "duplicate"
  else if status = kSubscription then
    set tCloudStatus to "subscription"
  else if status = kNotAvailable then
    set tCloudStatus to "no longer available"
  else if status = kNotUploaded then
    set tCloudStatus to "not uploaded"
  else if status = kError then
    set tCloudStatus to "error"
  else
    set tCloudStatus to "unknown"
  end if
end tell

display dialog tCloudStatus

To avoid value in raw code via the osascript command:

Save the script in the text format (not compiled)

osascript /path/to/myscript.applescript

Or, use the osascript command with the -e switches

osascript -e 'tell application "iTunes" to (cloud status of current track) as string' -e 'display alert "cloud status: " & result as informational'

Hello

Well, it is a known issue. AppleScript terminology is not usually loaded at run time but at compile time. Fortunately there's workaround.

To get termilogy string from constant at run time in complied script run in applet or run by osascript, you need to manually load terminology. One way is to issue a magic event ascrgdut (applescript get dynamic user terminology) in tell block targeted to the application of which termilogy is to be loaded.

The following script demonstrates how to use it.

--loadTerminology(me) -- to load global terminology such as OSAX. tell application "iTunes" activate my loadTerminology(it) -- to load the target application's terminology display dialog (player state as string) end tell on loadTerminology(a) (* reference a : reference of which terminology is to be loaded. *) try tell a to «event ascrgdut» -- (AppleSCRipt : Get Dynamic User Terminology) end try end loadTerminology

You may save this as a complied script and run it by osascript or save as an applet and run it, and see the effect of loadTerminology(). Without loading terminology, raw constant code will be shown, whereas with loading it, raw code is properly decompiled into corresponding terminology.

(Note that if you compile and execute AppleScript source code (.applescript file) by osascript, raw code is decompiled into terminology without calling loadTerminology(). This is because osascript loads terminology in order to compile the source code and no need to reload it at run time.)

Good luck,

H

PS. Although this and other methods already provided may work around the immediate problem, the terminology conflicts which cause the problem in the first place remain to be reported for correction.