BuyLog In
Bug Report T482725
Visible to All Users

Inconsistent keyboard handling in ColorPickEdit's popup form.

created 8 years ago

There seems to be a problem in using the repository item ColorPickEdit via the keyboard, esp. the Custom Color tab page. Please see the attached example project.

  1. In the first row the preselected color is Color.Black. This color is exactly the automatic color. When the Color Pick Edit is opened, the Web Color tab page is shown. When you select the Custom Color tab page, you can't use the cursor up/down buttons to navigate in the tab page.
    Whereas, when you open the Color Pick Edit in the second or third row, where the preselected color is not the same as the automatic color, the keyboard handling is correct.
  2. If the user specified a color in the "More Colors…" dialog on the Custom Color tab page, it is not possible to reach the "More Colors…" dialog via the keyboard any more. You may simulate this by clicking the button "Set Recent Color". Open the Custom Color tab page for the second or third row and try to navigate to the dialog "More Colors…".

Is there a solution for the problem?

Comments (1)
DevExpress Support Team 8 years ago

    Hi Kerstin,

    Thank you for the sample project. I've managed to reproduce the issues you are talking about. I'm forwarding this ticket to our developers for further investigation. I also want to note that it is possible to reach the "More Colors…" button even if there are recent colors displayed in the popup form. To do this, you need to navigate to the leftmost color in the "Standard Colors" list. After that, you will be able to move the cursor down. Yet, I agree that this is inconvenient behavior and it has to be fixed. Please bear with us. We will update this thread as soon as we have any news.

    Sign in to comment on this post

    Answers approved by DevExpress Support

    created 8 years ago

    We have fixed the issue described in this ticket and will include the fix in our next maintenance update. To apply this solution before the official update, request a hotfix by clicking the corresponding link for product versions you require.

    Note: Hotfixes may be unavailable for beta versions and updates that are about to be released.

      Comments (2)
      KS KS
      Kerstin Sodermanns 8 years ago

        Hello Pavel,

        thank you for the fix. I haven't tried it, yet, because we avoid using hot fixes if possible.
        Is there a workaround we can implement ourselves?

        Kerstin

        DevExpress Support Team 8 years ago

          Hi Kerstin,

          Though implementing the fix itself is not that difficult, it requires modifying some internal methods. At the same time, creating a workaround would require creating several custom descendants of our classes. If you urgently need to fix this issue and the described method is suitable for you, please let us know. We will try to create a workaround.

          Sign in to comment on this post

          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.