Serge_G

Damned ! As far as I remember I test these codes with Berlin version but not for mobile devices. I investigate, (check my old hard disk to remember my various tests) and found the problem but no solution yet. I was right it as to do with bitmap ! But I cheat a little . I don't know which source you use, hope it's the color demo one. Cheating : I add a bitmap to my Tprotypebindsource . I link this one to the image object of the list, doing that we don't need to create (and destroy) bitmaps. Finally I change my code procedure TForm1.ListView1UpdatingObjects(const Sender: TObject; const AItem: TListViewItem; var AHandled: Boolean); var AListItemBitmap : TListItemImage; AListItemText : TListItemText; AColor : TAlphaColor; begin AListItemBitmap:=AItem.Objects.FindObjectT<TListItemImage>('Image2'); AListItemText:=AItem.Objects.FindObjectT<TListItemText>('Text1'); if Assigned(AListItemBitmap) then begin // AListItemBitmap.Bitmap:=TBitmap.Create(40,40); try AColor:=StringToAlphaColor(AListItemText.Text) except // certaines couleurs sont inconnues! i.e. monneygreen, ltgrey AColor:=TAlphaColorRec.Null; end; AListItemBitmap.Bitmap.Clear(AColor); end; end; Don't forget to remove the onCloseQuery event And, as you can see, image attached, it works ! After this "ascertainment", I dug in the developpez.net forum and found this post i wrote. The goal is now to mix the two but how ?

Hum, here you touch a point "I am not a pear 😣" = "I don't have any Apple device (jealous)" so I could not check my code on these systems, I had to trust developpez.net technical correctors and some beta testers. None of them rise this behavior though ! Now, as far as I guess could be a problem with style, I ran in this problem when stylecollection have various entries. On another hand, I use a Bitmap (and I read somewhere Apple is not really fan of windows things) it's perhaps there a response

Using a list object (even an invisible one) is the easiest way but if you want to have a quick "SelectedItems.count" that's not the fastest way. Sleeping on my second option, using interface, I think it's the best one. Reviewing one Marco Cantu's lesson "Advanced Interface : Using Interfaces to Implement an Adapter Pattern" on Embarcadero Academy my opinion seems to be confirmed. // scheme interface ISelectedLstViewItems = Interface ['{A3A6DE5C-496B-4766-89FF-23F08EA5B329}'] function GetSelectedItems : TList<Integer>; procedure SetSelectedItem(Value : TList<Integer>); property SelectedItems : TList<Integer> read GetSelectedItems write SetSelectedItems; end; In my mind building an interface containing a SelectedItems as a TList<integer> and then overriding TListView as TListView = class(FMX.ListView.TListview, ISelectedLstViewItems) in another unit should do the trick. The only thing I don't know is "is it possible to use TagObject for the "link" ?" (even if it is a contraint) . Think I will test this with my SearchListViewInterface (for info you can follow my steps here) to sjordi "A quoi cela sert que Ducros il se décarcasse !"

I wrote various tutorials (and preparing some others) and blog post about TListView but in french you can read here https://serge-girard.developpez.com/ There are more than one solution to your goal 1- using a list object (i.e the color), yes it's one 2- using an interface to keep all items selected is another one you can use. I don't work on this part, currently working on customizing searching in TListView, but in my mind an interface should do the trick easily. Hum, seem a good subject if y have some times