dotnet / dotnet/wpf

Feature request: Add new "Negate" property in "Trigger" and "Condition" on use Trigger scene.

Open
#6,189 1 comment 3 reactions 0 assignees View on GitHub
Feature Request
Dominant language
C#
Stars
7.7k
Forks
1.3k
Avg merge
1d 11h
Merged PRs (30d)
61

Description

Sometimes we will need to use triggers to make some "not equals to value" scenarios (most common case: value is not null), but for such scenarios it is often necessary to add additional code in the code behind to achieve (such as add a "not" property in entity, or implement IValueConverter, even invert the default value).
But It seems that just adding a "Negate" property to the `Trigger` and `Condition` can makes everything easier.

Is it possible?? Or why not?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.