Normally when there are any server-side button click handlers attached to the UltraWebToolbar, a postback ensues. This property permits individual buttons to manage whether the control posts back in response to the end user clicking on them. The recommended use of AutoPostBack is to declaratively determine whether an individual button posts back at design-time, and use an event handler only when the determination to postback depends upon data known only at run-time.
Developers must leave this property set to its default value, true, if their application relies upon detecting button clicks on this button via a server-side button clicked event handler. Alternately, buttons of no interest to server-side event handlers may shunt what might be an unnecessary postback by setting AutoPostBack to false resulting in an improved client-side experience.
The client-side behavior of AutoPostBack respects client-side event handlers which may independently assign the needPostBack property on their event object to coerce a postback. This promotes backwards-compatibility with legacy applications already using needPostBack for this purpose.
AutoPostBack does not apply to TBarButtons that are grouped into a TBButtonGroup, therefore the property setting is ignored by grouped buttons.
When modifying AutoPostBack on the client-side, the change applies until a postback occurs. Developers should make no assumption about whether the modification will persist across postback, as the persistence of client-side changes to this property are formally undefined.
Target Platforms: Windows 10, Windows 8.1, Windows 8, Windows 7, Windows Vista SP1 or later, Windows XP SP3, Windows Server 2008 (Server Core not supported), Windows Server 2008 R2 (Server Core supported with SP1 or later), Windows Server 2003 SP2