4 replies to this topic

[Michael Cessna]

I've added a .Data property to the TRow class that is of the type Pointer...and am just checking to make sure it will not shoot me in the foot. Basically, I'm trying to replicate the idea of storing data in the same way a TListItem does (for TListView). I'd rather do this than store the data with the cell, if possible. Essentially, I have a collection of data (TCollection/TCollectionItem) where I'd like to associate a TCollectionItem with each row. So far, studying the NxCells unit, it looks like I'm going to be ok (though I realize future versions may break this idea). Any thoughts?

Thanks

Mike

[AIM]

I had the same idea when I started with NextGrid, see http://www.bergsoft....?showtopic=1529

Boki suggested the property ObjectReference which I use now, no need for a separate Data property...

[Michael Cessna]

Hi,

Thanks for your reply. I started out using the TCell.ObjectReference property, but found it a little cumbersome, since I didn't want to store an ObjectReference with each cell, or try to access another cell's ObjectReference property (when trying to use the ObjectReference of only one cell per row). The TRow class seems like the ideal place store data associated with a row; I'm just not sure if there are any scenarios where this will become problematic.

Mike

I had the same idea when I started with NextGrid, see http://www.bergsoft....?showtopic=1529

Boki suggested the property ObjectReference which I use now, no need for a separate Data property...

[Boki (Berg)]

Hello,

From next release there will be Row property (Row[Index]) and it will have Data (Pointer) property.

regards

[Michael Cessna]

Awesome, thanks!

Mike

Hello,

From next release there will be Row property (Row[Index]) and it will have Data (Pointer) property.

regards