Alternate method to hook up properties & events #671
+535
−157
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an experimental feature, trying to simplify the creation of new controls. In most cases this may even eliminate the need to declare an IHandler interface for the control.
This will probably be done for the 3.x series (which is a ways off)
Benefits:
Connector
in GTK (due to using static methods to wire up event handlers)ICallback
/Callback
implementationsEventManager.Register()
in the static constructorsIHandler
in cases where there are no methods and only properties and/or events.Drawbacks:
Widget.Properties
, accessing them may be slower (though this can be mitigated by pushing more functionality into subclasses of the native controls)Incomplete:
Style.Add<SomeHandler>(h => h.Control.NativeProperty = blah);
won't work