@joreg has an Idea, that it is probably more convenient to toggle Input Pins (one for every Enum Entry) instead of Or'ing Enums.
This of course relates not only to the windows, but many other widgets that has Flags.
Even more: many widgets use the same Enum, but use only several of its entries and ignore other.
Users have to check the documentation in order to know which Enum Entry has influence on a particular widget.
By providing Input Pins for the Entries, we do the job of picking what is relevant for every widget.
@joreg has an Idea, that it is probably more convenient to toggle Input Pins (one for every Enum Entry) instead of Or'ing Enums. This of course relates not only to the windows, but many other widgets that has Flags. Even more: many widgets use the same Enum, but use only several of its entries and ignore other. Users have to check the documentation in order to know which Enum Entry has influence on a particular widget. By providing Input Pins for the Entries, we do the job of picking what is relevant for every widget.
This is Or'ing for a Window:![image](https://user-images.githubusercontent.com/1189037/175835031-0acedbde-0714-4298-8f63-3cac36f5ce51.png)
'