-
Notifications
You must be signed in to change notification settings - Fork 667
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal: Expose IsActive and ActiveChanged event on StateTriggerBase #1460
Comments
Since StateTriggerBase is a |
That would make it publicly settable which I'm not sure is a good idea |
@dotMorten Sorry for the long delay here. This was put in the Freezer, but I'm also adding the needs-winui-3 label too. As I think you know we're working to get open source asap, and once that happens I think we'll have more ability to evaluate suggestions like this. I appreciate the time you took to file it Morten. |
Oh no worries. I wasn't expecting it until then. I'll be more than happy to implement it as well and submit the PR once the source is live. |
@dotMorten I know you have the PR open to add the StateTriggers to the toolkit, since they're more foundational - does it make more sense to wait and propose adding them to WinUI 3 instead? |
@michael-hawker No I didn't propose adding those triggers to WinUI. What I'm proposing here is to add the infrastructure that allows creating much more advanced state triggers - the PR you referred to does not have these advanced triggers because of the lack of that infrastructure - hence this feature request. |
Yeah, maybe |
@michael-hawker I think that ship has sailed :) |
@ryandemopoulos Any chance this could be re-evaluated for 1.1+ ? |
Should be noted that Continuing discussion for an alternative in CommunityToolkit/WindowsCommunityToolkit#4428 |
@Arlodotexe yes because that’s how you trigger that one. For this trigger you trigger it using the Value property |
Proposal: Expose
bool IsActive
andActiveChanged
event on StateTriggerBase.Summary
It's currently impossible to build composite state triggers because whether a state trigger is active or not can't be monitored, limiting their usage.
Rationale
I found it very useful in the WindowsStateTriggers repo, as I could make triggers that would trigger based on or/and/xor conditions of multiple triggers. I had to however add my own interface to my triggers to expose the Active property and ActiveChanged event, meaning my composite trigger weren't compatible with other 3rd and 1st part state triggers. It created some interesting capabilities like enabling/disabling UI if too many check boxes were checked etc.
Scope
Add the following to StateTriggerBase:
Important Notes
Here's an example how exposing these values allows more complex state triggers, by combining multiple"
![windowsstatetriggers](https://cloud.githubusercontent.com/assets/1378165/7996451/483cb19e-0ad5-11e5-9be8-a41aa2127fef.gif)
https://github.com/dotMorten/WindowsStateTriggers/blob/3a97a7a45b9c997e4f59e4afd98dc1ee7e0d8a49/src/TestApp/Samples/CompositeSample.xaml#L13-L49
The text was updated successfully, but these errors were encountered: