Skip to main content

ASPxCardViewBehaviorSettings.ProcessFocusedCardChangedOnServer Property

Gets or sets a value that specifies whether a change to the focused card should be completely processed on the server side.

Namespace: DevExpress.Web

Assembly: DevExpress.Web.v24.1.dll

NuGet Package: DevExpress.Web


public bool ProcessFocusedCardChangedOnServer { get; set; }

Property Value

Type Default Description
Boolean false

true to completely process focused card changes on the server side; false to have the capability to handle it on the client side.

Property Paths

You can access this nested property as listed below:

Library Object Type Path to ProcessFocusedCardChangedOnServer
ASP.NET Web Forms Controls ASPxCardView
.SettingsBehavior .ProcessFocusedCardChangedOnServer
ASP.NET MVC Extensions CardViewSettings
.SettingsBehavior .ProcessFocusedCardChangedOnServer


If the ProcessFocusedCardChangedOnServer property is set to false (the default behavior), the ASPxClientCardView.FocusedCardChanged client event is always fired in response to moving card focus, and no postback to the server occurs. This allows you to completely handle a focused card change on the client side. If you need to eventually process the event on the server side, you can set the event argument’s ASPxClientProcessingModeEventArgs.processOnServer property to true in an event handler. This initiates a round trip to the server and generates the corresponding ASPxCardView.FocusedCardChanged server-side event, which if handled, allows any desired server-side action to be performed. Note that a peculiarity of the ProcessFocusedCardChangedOnServer property set to false is that the ASPxCardView.FocusedCardChanged server event is initially fired on the server during the first grid control initialization (when the ASPxCardView.FocusedCardIndex property is set from -1 to a real value).

Setting the ProcessFocusedCardChangedOnServer property to true indicates that all processing of focused card changes should be performed on the server side, using the ASPxCardView.FocusedCardChanged server event, so a round trip to the server is always required. In this case, the ASPxClientCardView.FocusedCardChanged client event is not called on each change of the focused card. A peculiarity here is that the ASPxClientCardView.FocusedCardChanged client event is generated only once - on the first initialization of the client grid object.

See Also