I’m looking at collection of ~200 aliased notes in a table view pointed at an agent. With only four columns, I’m noticing that at least one of the columns (a short text field) is very slow to update when I edit a field. Possibly related, the text view panel is also very reluctant to show the text of the note I select in the table.
I was expecting similar behavior as if I were using the outline view. The document is responsive and all agents/rules appear to be executing cleanly.
Are my expectations for the table view wrong, or is there something I should examine that may be causing a problem?
It might help to expand a little on how much text is in each cell in the table. Are you editing in the cells. If attribute values are paragraph(s) of text that has the smell of a document design that might benefit from some review.
The number of items is a factor. I notice Outline+Column view is less snappy if I 100s of rows and 5–6 columns. Toggling the columns on only when needed helps. I also find that even if I show a column of data that is best for review, it’s generally faster easier to select the row and edit the value as a Displayed Attributes than mess in the column view. I suspect some of that likely applies to Table view, which I suspect may not be design-optimised for 100s of data rows as such is not necessarily common even if some of use use containers with large child counts a lot. UI that appears like a spreadsheet is not necessarily so.
That makes sense. I stripped the view down to two columns: $Name and $SceneIndex, each are just a handful of words. Since performance hasn’t changed, I’m probably pushing Tinderbox in a direction it’s not meant to go.
Another test, try the original layout with 50 items, do you see a difference?
I think we all have a tendency to turn extras on (I’ll just display another column) forgetting we can turn them off as easily. Out of interest, have you tried the same container in Attribute Browser view. That does seem to be happy with loads of records, though the displayed columns’ data aren’t (IIRC) editable in place (but can easily be a Displayed Attributes in the selected note.