Example
class DataItem
{
public int A{get;set;}
public int B{get;}
}
class Data
{
private DataItem[] _bb;
internal void AttachBB(DataItem[] bb)
{
_bb=bb;
}
public DataItem[] AA{get;set;}
public DataItem[] BB {get{return _bb;}}
}
AA property will be viewed as collection
BB property will be presented as string (type name)
Comments: ** Comment from web user: emartin **
class DataItem
{
public int A{get;set;}
public int B{get;}
}
class Data
{
private DataItem[] _bb;
internal void AttachBB(DataItem[] bb)
{
_bb=bb;
}
public DataItem[] AA{get;set;}
public DataItem[] BB {get{return _bb;}}
}
AA property will be viewed as collection
BB property will be presented as string (type name)
Comments: ** Comment from web user: emartin **
This is due to the, actual implementation of the CollectionEditor. This control still have bugs, and it's current implementation behavior is to be considered.
Strangely, the initial developer decide to "re-create" the list AND it's content when the editor is used, so the "get/set" property is needed to edit the collection, in order to "set" the new collection itself on save.
Although "AA" seems to work, it will fail when the collection gets really edited.