You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the problems of adopting Xamarin.Form after the poor customization of the controls, is certainly the little documentation of the internal archiving, which forces the developer to study how Xamarin.Form internals (Xaml Pareser, Xaml Compiler, Renders, ...) works before being able to publish a PR to correct a problem.
This discussion was converted from issue #135 on September 14, 2020 20:16.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Summary
One of the problems of adopting Xamarin.Form after the poor customization of the controls, is certainly the little documentation of the internal archiving, which forces the developer to study how Xamarin.Form internals (Xaml Pareser, Xaml Compiler, Renders, ...) works before being able to publish a PR to correct a problem.
I hope this does not happen in MAUI
API Changes
none
Intended Use Case
none
Beta Was this translation helpful? Give feedback.
All reactions