Changing Events to different Calendar in iCal

Patrick Stadelmann wrote:

  >>Basically, in iCal, I'm trying to move events that match a certain
  >>criteria from one Calendar to another. I've got my script cycling
  >>through all the events that I want to move, but I've got no clue how to
  >>move them to a different Calendar.
 >
 > Unless iCal provides a simpler way, the usual procedure would be to
 > gather the properties of the original event, and then create the new
 > event with the given properties. This is basically a copy, so if you
 > want to move the event, you'll need to delete the original afterwards.

Painful, but okay. How do I handle undefined values? For example:
set location of newEvent to location of oldEvent

Will cause a "iCal got an error: NSArgumentEvaluationScriptError" if the
oldEvent does not have a location associated with it.

-rev
 >> Stay informed about: Changing Events to different Calendar in iCal 

In article ,
rev <rev DeleteThis @TheWaterCooler.com> wrote:

 > Painful, but okay. How do I handle undefined values? For example:
 > set location of newEvent to location of oldEvent
 >
 > Will cause a "iCal got an error: NSArgumentEvaluationScriptError" if
 > the oldEvent does not have a location associated with it.

Use a try wrapper.

try
set location of newEvent to location of oldEvent
on error errMsg number errNumber --params are optional
-- handle error as necessary, to include simply ignoring the error
end try

--
Never play strip tarot.
 >> Stay informed about: Changing Events to different Calendar in iCal 

In article ,
rev <rev RemoveThis @TheWaterCooler.com> wrote:

 > Painful, but okay. How do I handle undefined values? For example:
 > set location of newEvent to location of oldEvent
 >
 > Will cause a "iCal got an error: NSArgumentEvaluationScriptError" if the
 > oldEvent does not have a location associated with it.

Use a "try / on error" block.

Patrick
--
Patrick Stadelmann
 >> Stay informed about: Changing Events to different Calendar in iCal 

99% there! But this question sort of feels like a potential bug in
Apple's stuff.

If I have an "allday event" then the "start date" property on the event
is one day before what I expect. So when I do a strict copy, the event
gets one day longer.

i.e.

If I have Christmas set as an all day event on "December 25", when I do
set oldStartDate to start date of oldEvent

It gets set to 4:00pm December 24.

So when I create the new event, it now spans from December 24th -
December 25th and has become two days.


e.g. Here's a script that creates an all day event for today (Thursday,
January 15th), but when I get back the start/end dates, the start date
is a day off (Wednesday, January 14th). Is that expected behavior?
----
tell application "iCal"
set testCalendar to ¬
(item 1 of (every calendar whose title is "Test"))
make new event at end of testCalendar with properties ¬
{end date:current date, ¬
start date:current date, ¬
summary:"Growing Date", ¬
allday event:true}

set myNewEvent to last event of testCalendar
display dialog "[" & (start date of myNewEvent) & ¬
"] to [" & (end date of myNewEvent) & "]"
end tell
----
 >> Stay informed about: Changing Events to different Calendar in iCal