Is there a particular reason why ListBoxRow and ListBoxColumn properties are readonly? It would be really nice to use the new iterator features and actually do something to the row/column in that iterator without having to go via a tag/counter and use the “old methods” to alter things.
e.g.
For Each row As ListBoxRow In Listbox1.Rows()
For Each column As ListboxColumn In row.Columns()
If column.Value = "2" Then
'listbox1.RemoveRowAt(2) 'works fine
'listbox1.CellValueAt(2, 0) = "MOO" 'works fine
'column.value = "MOO" 'doesnt work :(
End If
System.DebugLog(column.Value)
Next
Next
Probably iterator related and the reason is for 58500 (not visible in feedback)
if the modification must be done out of the loop there must be a property to let us understand the right coordinate (row, col) to work on
something like
For Each row As ListBoxRow In Listbox1.Rows()
For Each column As ListboxColumn In row.Columns()
If column.Value = “2” Then
listbox1.CellValueAt(column.path) = “MOO”
End If
Next
Next
Iterators have always been read-only. It’s not that they couldn’t be read-write but there are a lot of situations you then have to deal with so for now, they are read-only.
Select and Tab are showing as Read Only but when you drill down into those, they are shown as Get/Set[/quote]
I’ve just fixed the Selected and Tag pages. Thanks for pointing this out.