Re: [evolution-patches] cancel_component_dialog problem

["alfred.peng" <alfred peng sun com>]

Dear JP Rosevear,

   Thanks for your explanation.

   But in the source file 
calendar/gui/dialogs/send-comp.c(send_component_dialog) & 
calendar/gui/dialogs/cancel-comp.c(cancel_component_dialog), when we set 
the "CAL_STATIC_CAPABILITY_SAVE_SCHEDULES" sign, the return value of 
these two function are different.
   That's to say, when we cancel a event, sending a message to the 
attendees is the default action; But when we make a change to a event, 
no message sending is the default action.
   Why are they different? Or we should make them consistent?

Best regards
Alfred Peng

JP Rosevear wrote:

> On Sun, 2004-03-21 at 02:59, alfred.peng wrote:
>  
>
> > Dear Rodrigo,
> >
> > Would you please give me some advices?
> >
> > Maybe this inconsistency has some influence on our SUN backend
> > implementation.
> >    
>
> I believe this was put in because of the SunONE backend.  The sunone
> backend does scheduling itself as soon as the item is saved.  This check
> ensures just skips giving the dialog to the user when cancelling because
> if the item is being deleted it must be cancelled on the server.
>
> -JP
>