When deploying to certain platforms, under cetain circumstances, there is an exception that occurs in the DatePicker, TimePicker and a few other controls that rely on the same inner components. The stacktrace looks like it has to do with a default value for AppThemeBinding.
We have been developing our WPF app for some 4.5 years now and use the following controls from Telerik WPF UI control set:
I don't see these UI Controls on the Roadmap for MAUI and that is okay; it just delays our timeline for MAUI adoption. As we aren't a UI Component Control software development company we are dependent on folks like Telerik. This is not a complaint as much as it is just a let you know what some of your customers are doing. We need to be to be on the macOS desktop but native macOS development is very expensive. As a start-up that company that builds native desktop apps this is big deal and our investor take note of such things.
MAUI could help to reduce our development cost but only if we can move to that platform with UI Function set we have in our WPF App and to leverage engineering IP artifacts and development resource.
IsOpen = true,
IsOpen = false,
IsOpen = true,
IsOpen = false,
while the last IsOpen update isn't ready, kills the Popup.
It works async, even if animations are set to none/0s and there is no public event to validate the last update is fully done (Popup opened/closed)
In my case i have a popup opened, while a search operation is running in the background.
If this background search returns too fast and i set IsOpen to false, the update is ignored and the popup keeps in an opened state.
This is specifically a request for you to bring over the SignaturePad control from UI for Xamarin either as as a compatibility shim, or as a new native MAUI handler.
I am using the SDKBrowser app to demonstrate the problem. This does not happen on the emulator but on my physical device (Samsung S22). I have created a video and attached it.
When I enter a value into the Numeric input and click on the "." button, the entry does create a "," sign. This is fine but the cursor jumps back in front of the comma. I have to physically move the cursor back and can only then continue entering the decimal values.
The second problem is, if I accidently click the "." a second time after entering the decimal values, the app crashes.
I suspected it could be the language settings on the device. I am from South Africa and change the language of the device from English (South Africa) to English (United States) and then it works as expected. Regardless of this, I would expect the control to work with any culture.
A number of RadDataGrid properties can be successfully set in App.xaml, but setting others causes the control to display nothing -- at least in Android.
While I have not tested all possible settings, these results were found experimentally:
Can be used: BackgroundColor, DataOperationIndicatorMode, GridLinesThickness, HorizontalOptions, LoadOnDemandMode, Margin, MinimumHeightRequest, SelectionMode, UserSortMode, VerticalOptions, and ViewportBufferHeight.
Cannot be used in App.Xaml style: AutoGenerateColumns, GridLinesColor, GridLinesVisibility, LoadOnDemandBufferItemsCount, RowHeight, and SelectionUnit.