Reminder problems

[David Lewis]

I am trying out some simple fragments to get a feel for GCal4Ruby, and
I am having some problems with reminders.

* The example for setting a reminder given in the rdoc ...

event.reminder = {:minutes => 15, :method => 'email'}

is inconsistent with the internal documentation in the code, namely
that a reminder is specified with an array of hashes. So, what's
required is...

event.reminder = [{:minutes => 15, :method => 'email'}]

* After getting that call right, the following code...

require 'gcal4ruby'
include GCal4Ruby
service = Service.new
service.authenticate( acct, password)
event2 = Event.find( service, "hum bug")
event2[0].where = "xanadu"
event2[0].reminder = [{:minutes => 12, :method => 'SMS'}]
event2[0].save

... hangs during the save...

C:/Ruby192/lib/ruby/gems/1.9.1/gems/gdata4ruby-0.1.5/lib/gdata4ruby/
base.rb:126:in `do_request'
C:/Ruby192/lib/ruby/gems/1.9.1/gems/gdata4ruby-0.1.5/lib/gdata4ruby/
base.rb:122:in `do_request'
C:/Ruby192/lib/ruby/gems/1.9.1/gems/gdata4ruby-0.1.5/lib/gdata4ruby/
base.rb:94:in `send_request'
C:/Ruby192/lib/ruby/gems/1.9.1/gems/gdata4ruby-0.1.5/lib/gdata4ruby/
gdata_object.rb:153:in `save'
C:/Ruby192/lib/ruby/gems/1.9.1/gems/gcal4ruby-0.5.5/lib/gcal4ruby/
event.rb:225:in `save'
C:/Data/dev/Ruby/RubyProjects/RubyApplication3/lib/gcal-test-main.rb:
22:in `<top (required)>'
C:/Ruby192/lib/ruby/gems/1.9.1/gems/ruby-debug-ide-0.4.9/lib/ruby-
debug-ide.rb:109:in `debug_load'
C:/Ruby192/lib/ruby/gems/1.9.1/gems/ruby-debug-ide-0.4.9/lib/ruby-
debug-ide.rb:109:in `debug_program'
C:/Ruby192/lib/ruby/gems/1.9.1/gems/ruby-debug-ide-0.4.9/bin/rdebug-
ide:87:in `<top (required)>'
C:/Ruby192/bin/rdebug-ide:20:in `load'
C:/Ruby192/bin/rdebug-ide:20:in `<main>'
Uncaught exception: Internal Error

But the update to that calendar event's location is successful and the
reminder update unsuccessful. Removing the line to set the reminder
eliminates the hang.

Thanks. --David

[David Lewis]

Additional data point -- reminder works fine for a new event. Only
updating seems problematic.

That does open the possibility of a workaround -- instead of update,
do: read event, extract data, delete event, edit event, create "new"
event. But I'd still be grateful for help in doing reminders directly.

Thanks. --David.

[Mike Reich]

Hi David, thanks for the bug report. We're working on a fix out soon to deal with recurrence issues. Thanks to everyone who has written in with fixes and bug reports.

-Mike

Mike Reich
Seabourne Consulting
425-296-2440
mi...@seabourneconsulting.com