Xamarin.Forms 1.4.0.6341

Build native UIs for iOS, Android, and Windows Phone from a single, shared C# codebase

Install-Package Xamarin.Forms -Version 1.4.0.6341

dotnet add package Xamarin.Forms --version 1.4.0.6341

<PackageReference Include="Xamarin.Forms" Version="1.4.0.6341" />

paket add Xamarin.Forms --version 1.4.0.6341

#r "nuget: Xamarin.Forms, 1.4.0.6341"

Release Notes

## Important Notes ##

This is a feature release. As such unlike a patch version bump, the minor version bump indicates the inclusion of new APIs.

## New API ##

### ScrollView ###

It is now possible to detect the current scroll offset of the ScrollView. These are readonly bindable properties.
```csharp
public double ScrollX { get; }
public double ScrollY { get; }
```

There are also methods which can be used to perform scrolling in the ScrollView.
```csharp
public Task ScrollToAsync (double x, double y, bool animated);
public Task ScrollToAsync (Element element, bool animated);
```
The `Element` passed to `ScrollToAsync` must be a descendant of the `ScrollView` but does not have to be a direct child.

Finally for those who do not wish to use bindings to observe scrolling, there is a `Scrolled` event that fires when `ScrollX` or `ScrollY` are updated.
```csharp
public event EventHandler<ScrolledEventArgs> Scrolled;

public class ScrolledEventArgs : EventArgs
{
   public double ScrollX { get; } = 0;
   public double ScrollY { get; } = 0;
}
```
Lastly ScrollView no longer uses any internal API to communicate between the frontend and the renderer. `IScrollViewController`, which is implemented explicitly on ScrollView can be used to trigger these and other events.

### ListView ###

**Separator Enhancements**
It is now possible to enable/disable separators for the ListView. This can be configured via the `SeparatorVisibility` property, which is bindable.
```csharp
public SeparatorVisibility SeparatorVisibility { get; set; } = SeparatorVisibility.Default;

public enum SeparatorVisibility {
   Default = 0,
   None = 1,
}
```
Currently there is no option for `Always` as not all platforms have separators as part of their UX. We are considering adding this in the future, however it would be an invented paradigm for Windows platforms.

It is now possible to apply a `Color` to the separator in ListView.
```csharp
public Color SeparatorColor { get; set; } = Color.Default;
```
The default value is `Color.Default` and will function unchanged from the 1.3.0 implementation if left untouched. RGBA values are supported. This function does nothing in `SeparatorVisibility` is set to `None`. Please note that setting either of these properties on Android after loading the `ListView` incurs a large performance penalty.

**Header/Footer**
`ListView` has also grown both a Header and a Footer. These are managed through a series of properties which enable everything from simple usage to more complex MVVM style usage. With Header/Footer the primary reason developers have in the past been forced to put ListViews inside of ScrollViews is finally dead! If you are still placing a ListView inside a ScrollView we strongly suggest you consider porting.
```csharp
public object Header { get; set; } = null;
public DataTemplate HeaderTemplate { get; set; } = null;
public object Footer { get; set; } = null;
public DataTemplate FooterTemplate { get; set; } = null;
```
It is important to note that Header or Footer may be set directly to a View and the Template properties left null. This will cause the Header/Footer to be directly consumed by the renderer. All of these properties are bindable.

**Pull To Refresh**
PullToRefresh has been enabled on all current target platforms for ListView. To enable PullToRefresh in your app simple set `IsPullToRefreshEnabled` to true and make sure you respond to the correct events. It is important to note that this is the "easy" version of this API, in the future a more complete API with a standalone View may be added.
```csharp
public event EventHandler Refreshing;

public bool IsPullToRefreshEnabled { get; set; } = false;
public bool IsRefreshing { get; set; } = false;
public ICommand RefreshCommand { get; set; } = null;

public void BeginRefresh ();
public void EndRefresh ();
```
When the user triggers a `PullToRefresh` the Command will be invoked and the `Refreshed` event emitted. `IsRefreshing` will be set to true. The `ICommand.CanExecute` property is respected. The user must either call `EndRefresh` or assign `IsRefreshing` to false in order to end the refresh state.

All control parameters for these features and more are exposed through the IListViewController interface, which is explicitly implemented on ListView. This will assist those wishing to modify how these features work in custom renderers.

The Windows Phone implementation of PullToRefresh is a custom implementation as there is no platform idiom for doing this. In the future if the Windows platform decided to add a method of doing PullToRefresh by default, we intend to port.

### Forms.Application ###

The `Application` class now exposes 4 new events for dealing with Modal navigation.
```csharp
public event EventHandler<ModalPushedEventArgs> ModalPushed;
public event EventHandler<ModalPoppedEventArgs> ModalPopped;
public event EventHandler<ModalPushingEventArgs> ModalPushing;
public event EventHandler<ModalPoppingEventArgs> ModalPopping;
```
The `ModalPoppingEventArgs` contains a `Cancel` property which if set to true will cancel the Pop event and cause the application to enter the background (the operating system is informed of the unhandled back event).

In order to implement this feature, all pre-Application methods of creating a Forms app have been updated to create a default `Application` which is set as the root pages `Parent`. It is possible this may cause issues in some edge cases, if you have any issues please file a bug report. It is suggested you update your app to the new LoadApplication initialization methodology if possible.

Application now has a method of manually forcing the `Properties` dictionary to be saved to the IsolatedFileStore. This is to allow users to save their properties when it makes sense for them rather than risk them not getting serialized out due to a crash/being killed by the OS.
```csharp
public Task SavePropertiesAsync ()
```

### OpenGLRenderer ###

On Android `OpenGLRenderer` has been renamed `OpenGLViewRenderer` for consistency.

### Layout ###
Layout now contains a `ILayoutController` class which has an `IReadOnlyList<Element>` which can be used to enumerate the children of a Layout regardless of the type of the Layout.

## Other Features ##

- WebView now correctly supports javascript out of the box on Windows Phone 8.0

## Bug Fixes ##

- [Bug 27063](https://bugzilla.xamarin.com/show_bug.cgi?id=27063) - Navigation not always returning to the proper page.
- [Bug 27225](https://bugzilla.xamarin.com/show_bug.cgi?id=27225) - Secondary ToolbarItems cause app to hang during PushAsync
- [Bug 27437](https://bugzilla.xamarin.com/show_bug.cgi?id=27437) - [iOS] Context menu error after deleting an item from a ListView using ContextActions
- [Bug 27096](https://bugzilla.xamarin.com/show_bug.cgi?id=27096) - EntryCell has different fontsize on Android
- [Bug 21317](https://bugzilla.xamarin.com/show_bug.cgi?id=21317) - Stepper control .IsEnabled doesn't work on Android
- [Bug 26338](https://bugzilla.xamarin.com/show_bug.cgi?id=26338) - Unable to change page BackgroundImage from code
- [Bug 26588](https://bugzilla.xamarin.com/show_bug.cgi?id=26588) - [WinPhone] Entry does not trigger numeric keyboard when password masking is enabled
- [Bug 27072](https://bugzilla.xamarin.com/show_bug.cgi?id=27072) - Listview Context Actions not removed if a different item is tapped in Android

## Other Fixes ##

- Stepper default values now can be correctly inherited through a style.
- x:Static now correctly reports position on error in XAML.
- XAML now throws a more user friendly error on duplicate x:Name
- XAML will now use implicit operators when assigning values to properties
- XAML now supports baseclass indication for collection properties
- XAML string literals are now supported with `{}foo`
- iOS6 Modal pages should no longer sometimes have a 20px offset for no reason

Dependencies

• MonoAndroid 1.0

  • Xamarin.Android.Support.v4 (>= 21.0.3)

• WindowsPhone 8.0

  • WPtoolkit (>= 4.2013.8.16)

Used By

NuGet packages (1.7K)

Showing the top 5 NuGet packages that depend on Xamarin.Forms:

Package	Downloads
Xamarin.FFImageLoading.Forms Xamarin Library to load images quickly and easily on Xamarin.Forms. Ensure you call CachedImageRenderer.Init() on each platform!!! Features: - Xamarin.iOS, Xamarin.Android, Xamarin.Forms, Xamarin.Mac and Windows (WinRT, UWP) support - Configurable disk and memory caching - Multiple image views using the same image source (url, path, resource) will use only one bitmap which is cached in memory (less memory usage) - Deduplication of similar download/load requests. *(If 100 similar requests arrive at same time then one real loading will be performed while 99 others will wait).* - Error and loading placeholders support - Images can be automatically downsampled to specified size (less memory usage) - Fluent API which is inspired by Picasso naming - SVG / WebP / GIF support - Image loading Fade-In animations support - Can retry image downloads (RetryCount, RetryDelay) - Android bitmap optimization. Saves 50% of memory by trying not to use transparency channel when possible. - Transformations support - BlurredTransformation - CircleTransformation, RoundedTransformation, CornersTransformation, CropTransformation - ColorSpaceTransformation, GrayscaleTransformation, SepiaTransformation, TintTransformation - FlipTransformation, RotateTransformation - Supports custom transformations (native platform `ITransformation` implementations)	3.5M
Rg.Plugins.Popup Plugin for Xamarin forms. Allows you to open any page as a popup.	3.1M
Xamarin.Forms.Maps Maps models and renderers for Xamarin.Forms	2.6M
SkiaSharp.Views.Forms SkiaSharp for Xamarin.Forms is a set of views that can be used to draw on the screen.	2.2M
Syncfusion.Xamarin.Core This package contains common classes and interfaces that are used in other Syncfusion Xamarin UI controls. It also includes the following controls: 1. Text input control (aka floating label entry) - Decorates the input controls such as SfNumericTextBox, SfMaskedEdit, SfComboBox, SfAutoComplete, and Xamarin.Forms framework's Entry and Editor controls with password toggle icon to show and hide password, leading and trailing icons, and assistive labels such as floating label, hint, error, and help text. This control is supported in iOS, Android, UWP and WPF (Editor and Entry alone) platforms. 2. Border - Provides the rounded corner support with same and different corner radii on each side for any type of views. This control is supported in iOS, Android, UWP, and WPF platforms. 3. Gradient view - Provides gradient effect for any type of views. This control is supported in iOS, Android, UWP, and WPF platforms. 4. Avatar view - Provides a graphical representation for user image that allows you to customize the view by adding image, background color, text, etc. This control is supported in iOS, Android, UWP, and WPF platforms. 5. Effects view - Provides modern effects like ripple, selection, scaling, and rotation. Users can render these effects through touch interactions like touch down, touch up, long press, and also by calling the API. This control is supported in iOS, Android and UWP platforms. 6. Shimmer - Improves the responsiveness of an application by showing a modern shimmer effect when the data is being loaded in the background. This control comes with six built-in shimmer types along with custom view support. This control is supported in iOS, Android and UWP platforms. Note: This package needs to be installed in all Xamarin.Forms projects (.NET Standard, Android, iOS, UWP, macOS, and WPF). In addition, you need to install the “Syncfusion.Xamarin.Core.WPF” package for Xamarin.Forms WPF platform only. Support: Incident: https://www.syncfusion.com/support/directtrac/incidents/newincident?utm_source=nuget&utm_medium=listing Forum: https://www.syncfusion.com/forums/xamarin.forms?utm_source=nuget&utm_medium=listing This is a commercial product and requires a paid license for possession or use. Syncfusion’s licensed software, including this component, is subject to the terms and conditions of Syncfusion's EULA (https://www.syncfusion.com/eula/es/?utm_source=nuget&utm_medium=listing). To acquire a license, you can purchase one at https://www.syncfusion.com/sales/products?utm_source=nuget&utm_medium=listing or start a free 30-day trial here (https://www.syncfusion.com/account/manage-trials/start-trials?utm_source=nuget&utm_medium=listing). © Copyright 2021 Syncfusion, Inc. All Rights Reserved. The Syncfusion Essential Studio license and copyright applies to this distribution.	2.0M

GitHub repositories (294)

Showing the top 5 popular GitHub repositories that depend on Xamarin.Forms:

Repository	Stars
dotnet/maui .NET MAUI is the .NET Multi-platform App UI, a framework for building native device applications spanning mobile, tablet, and desktop.	6.4K
microsoft/ailab Experience, Learn and Code the latest breakthrough innovations with Microsoft AI	6.3K
dotnet/BenchmarkDotNet Powerful .NET library for benchmarking	6.3K
reactiveui/ReactiveUI An advanced, composable, functional reactive model-view-viewmodel framework for all .NET platforms that is inspired by functional reactive programming. ReactiveUI allows you to abstract mutable state away from your user interfaces, express the idea around a feature in one readable place and improve the testability of your application.	6.2K
xamarin/Xamarin.Forms Xamarin.Forms Official Home	5.2K

Version History