* Bring ImageButton API additions in line with current code
* [Core] putting things in better places
* [Core] first round of changes
* fix issue with checking if bindable properties are set
* Add fake Platform property to Page to keep Previewer happy: fixes#4351
* Make the fake Platform property internal
* Add unit tests to verify Previewer-required stuff in Core has not be changed
* Adding Obsolete to Page.Platform
* [Xaml] un-obsolete XamlLoader.Create
now that we plan to load Xaml files without compiling the ctor, keeping
XamlLoader.Create makes sense.
* [Xaml] add FallbackTypeResolver
* Additional tests
* More tests
* Further tests
* [Xaml] provide an mock App
* [C] allow re-registering implicit styles
* Some tweaks and reinstated test with missing resource key
* Add StyleAppliedToDerivedTypesAppliesToDerivedUnknownType test
* Renamed some stuff for consistency. Added some CSS tests.
* Remove use of ValueTuple
* Temporarily disable failing tests
* redirect valueprovider exceptions to the handler, allow the handler to intercept excpetion with Create()
* fix the CSS situation
* new callback, works for CSS
This changes the `ToolbarItem` constructor's `name` parameter to `text`, to match the non-obsolete `Text` that gets the value. Without the change, it's confusing when tracing data flow related to `Text`, since it doesn't appear at first that it's being set.
* fix issue#4262
Label HorizontalTextAlignment="Center" not working in conjunction with LineHeight on iOS
* Add missing parameter for macOS due to the previous method param change
* merge
* Added using UITextAlignment = AppKit.NSTextAlignment; as maintainability requested
* Revert "merge"
This reverts commit 939b6e1bc8ebd538af0db91dd8656e7eb2d31203.
* Revert "merge"
This reverts commit 939b6e1bc8ebd538af0db91dd8656e7eb2d31203.
* make test case more clear
* Changed the namespace for all the issues to Xamarin.Forms.Controls.Issues
* Moved some classes to Control directory with namespace Xamarin.Forms.Controls to fix conflicts after namespaces changes
* Fixed missed namespace for ButtonExtension
* Fixed namespace reference of Bugzilla42602 in WindowsUniversal/CustomRenderers.cs
GLib.Idle.Add enqueues functions in the main loop
with the lowest priority, so while the UI is updating
tasks will be queued in the main loop.
Using Gtk.Application.Invoke they are interleaved with UI
updates and handled with more fairness.
* ImageButton Implementation
* [Android] rename BorderBackgroundManager
* [Android] copy AspectFill changes to ImageButton
* [UITests] fix order of gallery pages to work with tests
* [Android] Account for changing image region with border/shadows
* [Android] check for api 18 and add setpadding call back in
* [Android] throw exception instead of crash when image fails to load
* Addressing issue comments and adding additional test cases to Issue demo
- fixes#1724
* Convert item to string, when ListView has no ItemTemplate
* ToStringValueConverter tests
* Format value using parameter in ToStringValueConverter
- fixes#3715
* fixes#1480
* Added test case
* Update Xamarin.Forms.Platform.iOS/VisualElementTracker.cs
Co-Authored-By: AndreiMisiukevich <andrei.misiukevich@gmail.com>
* updated test case
* [Core] Fix autosize elements in absolute layout
* revert the Hasflag extension
* - refactoring to the local UWP fix for Activity Indicator
- fixes#1399
* [GTK] Don't recreate master or detail if it didn't change
* [GTK] Fix several memory leaks using the Destroy pattern
Gtk objects must be disposed using the Destroy function that will
automatically iterate over the children and destroy them too:
https://developer.gnome.org/gtk2/stable/GtkWidget.html#gtk-widget-destroy
The gtk-sharp bindings discourage the use of Dispose and don't even call
the base class, leaving it without effect:
https://github.com/mono/gtk-sharp/blob/gtk-sharp-2-12-branch/gtk/Object.custom#L98
In the Controls, that inherits directly from native Gtk objects, the
overrides of the Dispose function are changed to override the Destroy
function. In the Renderers, that inherit from VisualElementRenderer,
the Destroy funtion is called in the dispose implementation so
subclasses only have to override Dispose (bool disposing) as they do
now.
* [GTK] Don't recreate the toolbar on each change
* [GTK] Fix leak connecting to the PropertyChanged event twice
Shane Neuville
Rui Marinho
E.Z. Hart
Stephane Delcroix
E.Z. Hart
Gerald Versluis
Pavel Yakovlev
Andoni Morales Alastruey
Edward Brey
Akihiko Odaki
masonyc
Andrei
Ione Souza Junior
Kevin Behrens
Rasto
Noam Yogev
Jason Smith