• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: "running" property causes Script Editor nervous breakdown
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: "running" property causes Script Editor nervous breakdown


  • Subject: Re: "running" property causes Script Editor nervous breakdown
  • From: Joe <email@hidden>
  • Date: Sat, 26 Apr 2008 10:05:30 -0700

Title: Re: "running" property causes Script Editor nervous breakd
Using System Events, processes works fine. I was playing around with the new 'running' property introduced with Leopard.

The script is not corrupt, or I should say writing it again and saving anew still results in the behavior I described.

Rebooting doesn't help either. It seems to be the one line of script I posted.

Every other AppleScript I have is still working properly so I don't think it is a system issue either.

Puzzling
Joe

On 08-04-25, at 16:14, Joe wrote:

One little line of script is causing really weird problems in Script Editor.

if not application "Safari" is running then tell application "Safari" to activate

Saved as a compiled script on the desktop.

Double-clicking the script to open it starts up both Safari and Script Editor, but opens no windows in either application. Double-clicking the script once again opens a window with the script's text visible, but the window is named "Window" not "test" or "test.scpt" as the file is named.

More misbehavior occurs if I try to change and save the script. The open and save box comes up, I click "Save"  and nothing gets saved. If I close "Window" then I'm asked to save which works.

Running the script does not activate Safari either. This part of the behavior will change and start working if I direct the script at Eudora rather than Safari. Eudora activates as it should.

I'm on Leopard and a G5 Power Mac.

Has anyone seen this? Is it a bug? Is my OS broken? Am I broken? Have I misread the page on the running property?

It sounds like your script's corrupt. What happens when you save the following as a separate script?

tell application "System Events"
        if not (every application process contains "Safari") then
                run script "tell application \"Safari\" to activate"
        end if
end tell


Philip Aker
echo email@hidden@nl | tr a-z@. p-za-o.@

Sent from my SE/30

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users

This email sent to email@hidden

  • Follow-Ups:
    • Re: "running" property causes Script Editor nervous breakdown
      • From: Philip Aker <email@hidden>
    • Re: "running" property causes Script Editor nervous breakdown
      • From: Bill Cheeseman <email@hidden>
References: 
 >"running" property causes Script Editor nervous breakdown (From: Joe <email@hidden>)
 >Re: "running" property causes Script Editor nervous breakdown (From: Philip Aker <email@hidden>)

  • Prev by Date: Re: "running" property causes Script Editor nervous breakdown
  • Next by Date: Re: "running" property causes Script Editor nervous breakdown
  • Previous by thread: Re: "running" property causes Script Editor nervous breakdown
  • Next by thread: Re: "running" property causes Script Editor nervous breakdown
  • Index(es):
    • Date
    • Thread