dodexahedron

Oh yeah I had meant to mention some issues that this may affect. Thanks. I have a couple more to add, I think (once I find where I stuck the...

Found em and added to the list

> Can you show a code example for a simple view event e.g. Button click? I think that would better articulate the proposal. Having both Action and event for the...

Initial findings about the current state of this: - There's a ton of coupling, currently, and lots of places that break encapsulation, which was only possible because of the public...

Woo that's good news. In that case, I will approach the event stuff as if Responder is already gone. The end result would be the same as the goal, anyway,...

Just a note about my last comment: Potential for merge conflicts exists (but easily-resolvable) since I'll be nuking the relevant events, methods, and properties from Responder early on in this...

Just noting here that this work will end up removing a significant portion of the remaining code in Responder. It includes moving the events, their wrappers, and the fields and...

I've implemented two events, so far, in code in my working copy (not pushed to the branch yet). One is a re-implementation of the OnVisibleChanged event, and the other is...

Addendum: Doing that could also optionally get rid of the separate `SetDesiredVisibility` method.

Something else potentially worth considering is whether a change in visibility on a View should inform all of its subviews to raise the events on themselves if their SuperView's effective...