I don't want to mention these things any longer if they are coming in the future. I guess I'm not so much curious about what is there today (although I am as well trying to learn how things work) but also how they expect to be. Properties exist in the traditional sense. I hope in the future releases this will be transparent for us. He mentioned writting his own properties on objects which simply call this method. If it is to be closer to WPF than Winforms/ASP.NET how does a control understand its child elements? Is there a collection? (if not available now, to be exposed in future releases?)Īlso another forum topic about the API Clumsiness, someone mentions property setting via SetValue(). If this is simply because of alpha and 'not done yet' no issuesĪs far as the last item. I don't see the possibility to override many methods/properties since they aren't exposed to be overriden. I understand theres no Paint method to override since we are vector here so makes sense. Concepts of Control.Controls collection for child controls. Override any properties/methods you may need to add any functionality to Basically in Winforms, 3 common things I believe would be used. I am not too familiar with WPF as of yet when it comes to writting controls. but from what I understand this community is for our feedback? I am just making vocal what I feel are shortcomings at this stage IMO in comparison to my past experiences writting controls. I have no problem with it being an Alpha.

Flowlayout margins