Hi jimmy,

I actually successfully replicated it, here is the always replicated behaviour if you interested

Input data with the same name more than 2 times affect other data with the same name when implemented in categorized list:

• at least 3 Data in the same category with same name: when user strike-through the third data , the first or the second data will be stroke
• at least 3 Data in the same category with 1 or more data in other category with same name: when user strike-through the data in other category, the second data in previous category will be stroke
• if you apply the again then removstrikethrough e, bugged strikethrough will dissappear

Hi Jimmy

Thank you for your information,

Please if there are any more question, feel free to ask!

Best Regards
Arief

Hi Cristobal,

First of all, you must create a Custom GridViewCell, because our GridViewCell doesn't have id that can be used to bind with the cell background, so you must make a Custom one including the id inside the layout.

Please remember that you only need this code inside your view model to access data from model and repository or local List<> : this.SourceItems = this.Repository.GetAll().ToObservable();

Next to connect with the background color, there are however there are two method to access the value from the data

First Method is you can manipulate your model by adding this:

 public StyleAttributes ColorStyle        {            get            {                return new StyleAttributes(){
                    BackgroundColor=(this.Color == Red)?Color.FromArgb(0xff,0xff,0x00,0x00):Color.FromArgb(0xff,0xff,0xff,0xff)

                };
            }
        }

Note you can change Color.FromArgb with our premade color using for example: Colors.Red or Colors.Transparent, also remember to add 0x before hex code because it only accept byte

Then inside your binding provider you can add:

itemBinding.AddBinding("YourCellBackgroundID", BindableProperties.StyleAttributesProperty, new BindingDescription("ColorStyle"));

This could be done because when you can call List/Grid type you can also access your model from there

Another method you can use is converter:

Add this inside your binding provider:

itemBinding.AddBinding("YourCellBackgroundID", BindableProperties.StyleAttributesProperty, new BindingDescription("Color"){ Converter = new ColorConverter()});

Make new file named ColorConverter with class ColorConverter and insert this inside:

	public class ColorConverter: IValueConverter
	{
		#region IValueConverter implementation

		public object Convert(object value, Type targetType, object parameter, CultureInfo culture)
		{
			if (value is String)
			{
				int CatColor = (String)value;

                if (CatColor == "Red")
                {
                    StyleAttributes style = new StyleAttributes();

                    style.BackgroundColor = Colors.Red;
                    return style;
                }
                else 
                {
                    StyleAttributes style = new StyleAttributes();

                    style.BackgroundColor = Colors.White;
                    return style;
                }
			}

			return null;
		}

		public object ConvertBack(object value, Type targetType, object parameter, CultureInfo culture)
		{
			throw new System.NotImplementedException();
		}

		#endregion
	}

Connect your binding provider with this converter

So in conclusion, i think the second method is more cleaner and doesn't manipulate the model too much... The only file you actually need to changes is just the Layout and Binding Provider (also model or converter)

You can also see this kind of implementation in our samples: http://git.intersoftpt.com/projects/CROS/repos/samples/browse/MyInventory

Hope that helps :)

Best Regards,
Arief

Hi Jimmy, 

Looks like the problem have already been fixed by our programmer in the newest version (Crosslight 3.0.5000.226) it contain bug fixes for ListFragment (for example like navigation to the same view model bug) also please be aware that we also updated some of our samples.

I use version 226 and data samples with drawer, i modified the samples to use nested list (list navigate to more list then to detail) and it is working :) (217 not working and send error like your samples)

If the problem still persist please inform us thanks :)

Best regards, 
Arief

Hi Jimmy

Thanks for your information. I have report this to Crosslight development team under 'CROS-793'. I will update you with information about this issue.

Best Regards,
Arief

Edit: typo issue number