Replies: 1 comment
-
I don't believe so.
The table browser maintains two bits of state on an item, selected and deleted. TB.MAP.SELECTED.ITEMS, TB.MAP.DELETED.ITEMS, or TB.MAP.ITEMS let you map over those sets, or you can TB.COLLECT.ITEMS -- which takes either a predicate function, or the special values 'SELECTED or 'DELETED which give you those subsets. DELETED items are displayed lined-through and don't participate in selection extension. There's a TIDATA field of a TABLEITEM which lets you store an arbitrary object if you need to associate other data with the items. The TABLEBROWSER was extracted and generalized from the original implementation in the FILEBROWSER - which is why it has the DELETED item state and behavior. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Is it possible to configure TableBrowser so that only one item at a time can be selected and multiple selection is not allowed?
In general, once one or more items are selected what is the proper way of accessing them? Calling
TB.MAP.SELECTED.ITEMSto iterate over the items?Beta Was this translation helpful? Give feedback.
All reactions