[DevExpress Support Team: CLONED FROM B232418: TdxBarButton does not always synchronize its Down property value with the Checked property of a TAction linked to this bar button]
Hello!
Version 2014 2.4 - not work!
Work only with AutoCheck = True Property in the TAction.
Ticket
T256528
Visible to All Users
Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
I have tested the example provided in the TdxBarButton does not always synchronize its Down property value with the Checked property of a TAction linked to this bar button ticket with the latest version of our controls and it seems to work OK now. This likely means that the problem reported in the context of that ticket is solved. The scenario you reported (when it is necessary to enable the AutoCheck property) seems to be related to the following tickets:
Ribbon: Buttons with actions attached and GroupIndex set (radio style) can't change their Down property with a click
dxLargeButton's Down property doesn't change after clicking it if it has an Action
Please check these inquiries. If the issue you reported is the same as the one mentioned there, this behavior is by design. The AutoCheck property should be enabled to implement that behavior.