Thanks for watching! Let me know what kind of controls you're thinking of making, and I hope this helps you out there! Also check out the blog post in the description from Pedro Jesus on the Microsoft Blog, it talks about these topics further! 🕘Timestamps: 00:00 - Video Start 00:25 - My Circular Button Custom Control 01:58 - How to Create the Control's Class 04:47 - The OnPropertyChanged Methods 07:31 - How to use your Custom Control 10:02 - One Quick 'Gotcha' I Ran Into
You should see a bindable property (comparable to a dependency property in WPF and UWP) as a kind of unique key (but with associated settings and behavior). Each MAUI control has a dictionary of bindable property keys and values. If a control has no value set for a specific bindable property, let's say for "IsVisibleProperty", it will not take up memory for that instance. Calling the non-static getter of "IsVisible" will call GetValue() which will look up the value in the dictionary for the key "IsVisibleProperty". If it does not find that value, it will return the default value as described in the definition of the static bindable property "IsVisibleProperty". That's why the bindable property itself is static, it's a shared "key" between all instances of the class.
I created a Circular Button (called a Fab - Floating Action Button on Android) using a Grid. It looked OK but didn't respond to a user tap. Now, I've copied your ScaleTo & Easing code and it reacts in a pleasing way that gives the user feedback it has been clicked.
I'm working on a radial dial control it's for a opensource project in mixed reality.Trying hidden buttons where you drop all color from a control and tying swipe control on the button right button swipe down rotates clockwise swipe up rotates anti clockwise left button is opposite. Problem is keeping the state of the dial it's easy to use rotate animation but controlled rotation is harder to implement.
Do you recommend MAUI for production? Im about to start a new app, i had bad experience with Xamarin, i dont to use it anymore so im considering other tecnologies.
Yeah, that’s a good question. In Microsoft’s opinion, it’s ready to go. I think for me, it depends on the complexity of the app, along with how much “framework bug tolerance” you have. Maui still does have a lot of little bugs, and if those things turn you off, then another, more established framework may be better. But that will also get better with time. I think I’ll probably use Maui until I find a reason not to, since it’s just what I’m most familiar with at the moment. Especially if the F# support improves, since it is lacking, tooling wise. Hope that makes sense.
