• 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: Mavericks, Calendar, Applescript alarms
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Mavericks, Calendar, Applescript alarms


  • Subject: Re: Mavericks, Calendar, Applescript alarms
  • From: Jan <email@hidden>
  • Date: Fri, 07 Feb 2014 09:23:09 +0100

> On 07.02.2014, at 06:59, Dee Dee Sommers <email@hidden> wrote:
>
> Ugh.
>
> Hi!
> Well I THOUGHT I knew a work-around.  Except that was from my testing on a test system, not my actual mission-critical live system. :-)
> For the refresher, I just updated a MacPro from Mountain Lion to Mavericks.
> So here is the problem I seem to be encountering with my existing Automator and Applescript applications that I use to set alerts in Calendar to interact with Wirecast, etc.:
> First, it looks like all the events are still there (in Calendar), except they lost their link to what they are supposed to be doing!
> So I need to go back in and open each one (most of them are repeating events, so theoretically I only need to open one of each of those).
> Anyway, when I click to tell the event to set an alarm to fire at the time of the event and to open a file, the default is Calendar.  I can click on "other" and *hopefully* that will open a browse selection window that I can navigate to the script application or automator workflow/application, for selection.  And then save.
>
> But this is not what always happens.  Many times when I click on "other", NOTHING happens.  I just get to tell the little dialoge windowy thing that I want it to happen at the time of the event and either click cancel or save.  Then if I go back into it, the file selection has changed back from "other" (without opening a selection window), to Calendar.  That isn't working too well for me.
>
> I tried making a new event to specify the file to open that way:  same behavior. :-\
>
> But on a couple of the old events, I WAS able to tell it exactly what I want ti to do and when.
> The other thing is that on the couple that do seem to be working, [at they were a few minutes ago], I think they work because I opened those apps from the finder during the course of my trying to figure out what is going on.
>
> So basically, pretty much all my applescript alarms are on hiatus right now.  But I don't know how to fix them.
> Any kind suggestions would be greatly appreciated!
>
> Thank you!
> Dee Dee

I haven't followed the topic to this date so apologies if that was already covered~
Have you already tried basic Calendar troubleshooting?
Archive > wipe > import?

bye, jan
 _______________________________________________
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


References: 
 >Mavericks, Calendar, Applescript alarms (From: Dee Dee Sommers <email@hidden>)

  • Prev by Date: Mavericks, Calendar, Applescript alarms
  • Next by Date: Why these errors?
  • Previous by thread: Mavericks, Calendar, Applescript alarms
  • Next by thread: Why these errors?
  • Index(es):
    • Date
    • Thread