Steven Kirk

> Not yet supported, readonly for now. This isn't true, edit mode is there, but it's untested in the sample so may well be that it's broken. Will take a...

Converted to draft.

@ionoy does `Enter/ExitActions` refer to mouse over? If so, there is the `:pointerover` pseudoclass (which I'm actually thinking we should rename to `:hover` like in HTML): ```xml ```

As an aside, in longer term thinking I'd love to be able to have expressions in bindings so you could do stuff like (totally inventing a syntax on the spot...

I've been working a bit in WPF and got reminded where triggers can come in useful, especially data triggers: ```xml ``` I don't think WPF's syntax is very nice here...

I've been thinking about this some more and I think allowing more powerful expressions in bindings would be preferable to triggers, and not a whole lot more work. Regarding syntax,...

@Xarlot please note that we've not made a decision to not include triggers, we're just exploring alternatives. I've taken a look at your examples and a lot of that can...

> I think if we were able to access the DataContext frome a selector we can cover everything that a wpf trigger is able to do for us. That would...

Afraid not, we've been putting out fires left and right to try and get 0.10 released. Hopefully once that's out I can start work on it.

@MopsiMauser for the moment you can use behaviors: the [AvaloniaBehaviors](https://github.com/wieslawsoltes/AvaloniaBehaviors) repository has the `DataTriggerBehavior` that I think does what you want. See examples here: https://github.com/wieslawsoltes/AvaloniaBehaviors/blob/master/samples/BehaviorsTestApplication/Pages/DataTriggerBehaviorControl.xaml