Hello Yudi,

your proposed workaround solves the problem.

Thanks,

Thomas

Hello Yudi,

Thank you for the sample. You did it almost like I did. Please, make the following changes to reproduce the problem:

Item.FormMetadata.cs: Move the Sold section up to appear directly under the general section. This is for better visibility only.

[Section(Style = SectionLayoutStyle.ImageWithFields)]
public static GeneralSection General;

[Section("Item Status")]
[VisibilityBinding(Path = "IsNewItem", SourceType = BindingSourceType.ViewModel, ConverterType = typeof(BooleanNegateConverter))]
public static SoldSection Sold;

ItemEditorViewModel.cs: Remove this.Item.HasReminder = true; from Navigated. Change

private void ExecuteViewLargeImage(object parameter)
{
	this.Item.HasReminder = !this.Item.HasReminder;
	//this.NavigationService.Navigate(new NavigationTarget(typeof(ItemDetailViewModel), "PhotoDetail", new NavigationParameter(this.Item)));
}

After applying these changes start the app. Select a list item. No sold date is visible which is OK. Execute View Larger command through the image picker. No sold date is visible. Navigate back to the list and select the same item again. Now, the sold date is visible. Execute View larger. Sold date is still visible. Navigate back to the list and select the same item again. Sold date is gone.

So, doing the binding in on Navigated works, because you are in an early stage. But after the view is created the binding has no effect.

I hope this helps to reproduce the problem.

As usual you will create a new CROS ticket for the dev team after reproducing the bug. This is the way it should be. The worse thing about it is that it will take weeks or months to get the fix. Currently there is no public release schedule for Crosslight and no feature roadmap. This is a bad situation for Crosslight developers. Please, keep up a reliable release cycle of 4 weeks like you did with Update 1 and 2 of Crosslight 5.

Thanks,

Thomas

This one is still not answered.

Hello Yudi,

Thanks for your explanation. But how could I know this. Is there any documentation about this. If I am in a solution and upgrade the NuGet packages, I get this version mixture automatically. Without a hint from your side, I am lost. Please, do not turn Crosslight into such an expert system.

Thanks,

Thomas

Hello Yudi,

I just did a quick test and your provided solution could be build and deployed to a test device at my end. So this configuration works.

I upgraded all Crosslight NuGet packages to the latest stable version in my test scenario, because I thought they play well together. Here is my packages configuration:

<?xml version="1.0" encoding="utf-8"?>
<packages>
<package id="Crosslight.Xamarin.Android.Support.Animated.Vector.Drawable" version="23.4.0.1" targetFramework="monoandroid50" />
<package id="Crosslight.Xamarin.Android.Support.Design" version="23.4.0.1" targetFramework="monoandroid50" />
<package id="Crosslight.Xamarin.Android.Support.v4" version="23.4.0.1" targetFramework="monoandroid50" />
<package id="Crosslight.Xamarin.Android.Support.v7.AppCompat" version="23.4.0.1" targetFramework="monoandroid50" />
<package id="Crosslight.Xamarin.Android.Support.v7.CardView" version="23.4.0.1" targetFramework="monoandroid50" />
<package id="Crosslight.Xamarin.Android.Support.v7.RecyclerView" version="23.4.0.1" targetFramework="monoandroid50" />
<package id="Crosslight.Xamarin.Android.Support.Vector.Drawable" version="23.4.0.1" targetFramework="monoandroid50" />
<package id="Intersoft.Crosslight" version="5.0.5000.706" targetFramework="monoandroid50" />
<package id="Intersoft.Crosslight.Android.v7" version="5.0.5000.706" targetFramework="monoandroid50" />
</packages>

Why do the Crosslight.Xamarin.Android.Support libraries cause these problems and how could I know that this is a problem?

What are these "Vector.Drawable" libraries? Is it a new feature? Where is the documentation?

Thanks for clarifying and the provided fixes.

Thomas