Why does the advanced form have to work the way that it does? What I mean is, if I've understood correctly, the advanced form is actually just another part of the scheduler itself and so updating the advanced form, is, in fact, an update of the scheduler itself.
I wonder if it is not possible to completely divorce the advanced form from the scheduler completely. that is, have a completely independent page that queries and updates the data store directly, taking only an indication of the mode and maybe the ID of the appointment to be edited from the scheduler when it is called, maybe via the query string.
OK, it would, I suppose, mean that the code currently in the scheduler for handling the data store operations for an update would have to be moved but updates to the scheduler itself, if needed could be stimulated using the OnClientClose callback function of the window holding the new advanced form.
I wonder if there is the ability already to do it this way as I note that the SchedulerFormMode enumeration has a "Hidden" value. I'd like to know what that's for.
I guess I'd have to catch a number of the client-side events to stop the built-in functionality from kicking in, but I'd imagine that that is quite doable.
I'd like to hear from someone at telerik towers on the above, especially on the idea of suppressing the built in forms.
--
Stuart
I wonder if it is not possible to completely divorce the advanced form from the scheduler completely. that is, have a completely independent page that queries and updates the data store directly, taking only an indication of the mode and maybe the ID of the appointment to be edited from the scheduler when it is called, maybe via the query string.
OK, it would, I suppose, mean that the code currently in the scheduler for handling the data store operations for an update would have to be moved but updates to the scheduler itself, if needed could be stimulated using the OnClientClose callback function of the window holding the new advanced form.
I wonder if there is the ability already to do it this way as I note that the SchedulerFormMode enumeration has a "Hidden" value. I'd like to know what that's for.
I guess I'd have to catch a number of the client-side events to stop the built-in functionality from kicking in, but I'd imagine that that is quite doable.
I'd like to hear from someone at telerik towers on the above, especially on the idea of suppressing the built in forms.
--
Stuart