The BeforeEventRenderEventArgs for the DayPilotMonth doesn't include a <b>ContextMenuClientName</b>.
Is there another way to have different context menus assigned to different events in the DayPilotMonth?
Simon Edwards
-
3/12/2008 1:59:31 PM
Thanks, that'll help but I'm coming to the conclusion that I'll also need greater flexibility in the waytheresulting 'EventMenuClick' is handled. For example, it's possible to handle other 'Event' Events ;) through Javascript orPostback. But once we've set the EventRightClickHandling to ContextMenu, it seems the resulting click can then only be handled server-side through the passing of a command to the Server-side event.
Unfortunately, one of the things I need to do when the user clicks on one of the context menu options, is to load a page as a 'modal dialog' which I can only seem to do through client-side javascript using openWindow... and can see no way of instagating this from the server-side click event.
At the same time as bringing the DayPilotMonth up-to-date as regards context menu functionality, is it also possible to look at providing both a client-side and server-side option for the handling of the resulting 'click'?
At present, I'm adding 'links' to the Bubble as a way of providing an alternative to right-clicking, so you just hover over the event on the month control, then select 'Properties' (for example), and a modal properties form is displayed - it's not exactly what I want, but at least the bubble rendering allows me to construct a menu inside the bubble which is different for each event too.
Simon Edwards
-
3/13/2008 4:24:18 PM
Each menu item has a property that determines it's handling. See also the example from Demo/Calendar/Default.aspx:
<daypilot:daypilotmenu id="DayPilotMenu1" runat="server">
<DayPilot:MenuItem Text="Open" Action="JavaScript" JavaScript="alert('Opening event (id {0})');" ></DayPilot:MenuItem>
<DayPilot:MenuItem Text="Send" Action="JavaScript" JavaScript="alert('Sending event (id {0})');" ></DayPilot:MenuItem>
<DayPilot:MenuItem Text="-" Action="NavigateUrl" ></DayPilot:MenuItem>
<DayPilot:MenuItem Text="Delete (CallBack)" Action="Callback" Command="Delete"></DayPilot:MenuItem>
<DayPilot:MenuItem Action="PostBack" Command="Delete" Text="Delete (PostBack)" />
<DayPilot:MenuItem Action="NavigateUrl" NavigateUrl="javascript:alert('Going somewhere else (id {0})');" Text="NavigateUrl test" />
</daypilot:daypilotmenu>
The Action attribute determines how an item will be handled (it can be CallBack, PostBack, JavaScript, and NavigateUrl).
EventMenuClick is executed only if you click on a menu item with Action="CallBack" or Action="PostBack".
Is that what you are looking for?
Yes, exactly that. Thanks.
Simon Edwards
-
3/13/2008 7:35:30 PM
We're up to 4.9, and there's still no custom event context menus on daypilotmonth. When can we expect that?
James Daniel
-
7/25/2008 8:33:20 PM