An example demonstrates a wide range of client events that
can be used to control scheduler operation without accessing a WWW server. Performing
various operations on a scheduler such as changing widths of panels and columns,
editing texts, moving SchedulerItem objects, changing periods, you can
see entries displayed in a right part of a window. Entries denote subsequent client
events to be programmed and handled in JavaScript and do not cause
calling server code.
A way particular event operates is determined by values of appropriate Sch.EventXXX
properties (such as EventRowTextEditing, EventItemDragged, etc).
These properties return objects describing what happens on a client and a server.
Setting a Sch.EventXXX.ClientScript property you can set JavaScript
code to be executed after an event is called.
In an example above this code causes only calling a client JavaScript add()
method that adds a text message identifying a given event on a right side of a browser
window using DHTML.
Mouse events assigned to various areas of a scheduler are handled in a similar way.
DefaultItemStyle, CaptionStyle, TimeLineStyle properties
allow to configure a way different areas of a control look like. It is also possible
to set JavaScript handling mouse events occuring on an area. A XxxStyle
property contains EventXxx properties, allowing to handle mouse events
such as Click, DblClick, MouseDown, MouseUp,
MouseMove, MouseOver, ContextMenu. Ex. a Sch.CaptionStyle.EventClick
event is called when a mouse is clicked on a title of a scheduler while Sch.BodyStyle.EventContextMenu
event before a context menu is opened on a main grid of a scheduler.
If you would look into a
source code
for this demo, click on the link.
For demonstration purposes all appointments displayed on a calendar are stored in
ASP.NET session objects, so original values are restored immediately after a new
session object is created.
A list of appointments and resources is intialized every time a new session is started.
|