WatermarkComboBox background and selection issues after 4.4.0

Open
#1,729 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
desktop

Research direction

Start by inspecting the WatermarkComboBox and its WPF style or template, comparing behavior with and without a Background after version 4.4.0. Reproduce the missing default background, mouse activation, and hover behavior; done means the default style is preserved and custom backgrounds do not remove hover feedback.

Written by the indexing model from the issue text.

Description

Thanks for this library ♥

4.4.0 introduced the possibility to set the background brush of the WatermarkComboBox. But this seems to have brought some issues;

  1. There is no default background, and the combo box ends up transparent if not setting a background.
  2. When not setting any background, the ComboBox is hard to activate with the mouse:
    • Mouse is often not captured, and you have to move the mouse out and the back in slowly to get it to capture.
    • When mouse is not captured, clicking inside the box has no effect.
  3. When setting a background to workaround 2. above, the default hover-effect is removed, making the control feel disabled.
    (The hover effect works as expected when not setting the background, when you get the mouse to be captured)

Any tips on how to resolve or work around this would be greatly appreciated!

My preferred functionality would be to have a default background matching the default WPF style, and when setting a background the hover-effect to still be there.

Dominant language
C#
Stars
4.2k
Forks
912
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from xceedsoftware/wpftoolkit

All issues in xceedsoftware/wpftoolkit

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.