Table of Contents
- Getting Started
- EO.Pdf
- EO.Web
- EO.WebBrowser
- EO.Wpf
- Common Topics
- Reference
- .NET API Reference
- JavaScript API Reference
- EO.Web
- EO.Web
- Objects
- Global Functions
- Global Functions
- eo_Callback
- eo_CancelBubble
- eo_CancelEvent
- eo_DateToString
- eo_FormatString
- eo_GetContainer
- eo_GetEventPos
- eo_GetNavigatorEventInfo
- eo_GetObject
- eo_HideAllPopups
- eo_MsgBox
- eo_RegisterDragTarget
- eo_SetComboBoxValue
- eo_ShowContextMenu
- eo_ShowPopup
- eo_ShowPopupCalendar
- eo_StringToDate
- eo_TriggerServerEvent
- eo_UnregisterDragTarget
- Event Handlers
- EO.WebEngine
- EO.Web
eo_Callback Function |
Manually triggers a client side callback.
Parameters
- id
- The ID of the Callback control, see remark section for details.
- param
- Optional parameter for the callback. The parameter will be available through CallbackEventArgs.Parameter when the callback reaches the server side.
Return Value
-
Returns true if the callback was successful, otherwise false.
Usually you do not need to call this function to trigger a callback. Use Callback.Triggers or CallbackPanel.Triggers to specify the trigger and the callback will be automatically triggered. Alternatively, you can use this function to manually trigger a callback:
<div onclick="eo_Callback('callback1', 'test')">Test Callback</div>
<a href="javascript:void eo_Callback('callback1', 'test')">Test Callback</a>
Usually you can use the ID of the server control as the id parameter to call this function. However, when two server controls resides in different naming containers (for example, two user controls), it's possible for them to have the same ID. In this case you should use the value of the ClientID of the Callback control as the id parameter. You may need to use a debugger to find out the ClientID value.
The function returns true if the call were successful submitted. The call returns false when:
- Two many previous callbacks are already queued up on this same Callback object, or;
- Parameter id is incorrect.
Client side event handler Callback.ClientSideBeforeExecute, if supplied, will be called before this function returns. However, Callback.ClientSideAfterExecute is not guaranteed to be called before this function returns since the actual callback executes asynchronously.