Has anyone figured out a way to see what index you are changing when editing a long list of data.
I know I could use replace index but I am changing them so often it would be helpful to simple open the edit panel and visually see which index I am changing.
See some of @Joseph_Oster replies in this thread:
A caveat to using the vuTreeList tool is that geometry can get in the way of seeing its blue and yellow results. Either previews from other components or worse, Rhino geometry which must be hidden. A related post is this one that adds a button to select a list of items.
Would still be cool to have a srollable list that works like a self-contained list item.
*** Scrolling through the list highlights the item geometry
*** Could even select items in the list to create outputs for those items
Easy to find and select.
An interesting idea, though it looks complicated. 1-based items instead of 0-based is unconventional, eh? More significantly, are you suggesting two methods for scrolling?
Thatâs a departure from UI norms that could be confusing. Does the cyan rectangle move to stay visible when using the scrollbar? Scrolling a list of interactive elements (checkboxes) is also non-standard, isnât it? Seems more difficult to implement than scrolling a static list.
I have long wished for the ability to designate UI elements in a cluster as âexternalâ, which would make them appear on the surface of the cluster. Not sure how they are arranged (by groups?) but the cluster would grow larger to accommodate them.
As to the pt_select_2020Dec7b.gh idea posted above, the text in that old post says âit is removedâ but thatâs a poor explanation, only true of the Cull Index component (green group, top right).
At the bottom right is a List Item component showing selected points as green. So as it says of selected items:
though it looks complicated. 1-based items instead of 0-based is unconventional, eh?
That was me being lazy. Would still be the usual 0-based.
More significantly, are you suggesting two methods for scrolling?
I think just some way to scroll through a long list. Cyan was more just a static highlight to indicate whichever item is currently being scrolled over so that if youâre scrolling through a list of 200 points you can easily see the correlation between where the list is and which point is currently highlighted in the viewport.
The radio buttons were possibly a way to select items in the list and have automatic outputs created for them to eradicate the need for an input of indexes. But even without all the selection stuff just a scrollable list would be useful - make it easy to find objects in a sea of objects.
A pair of zero to one sliders has done that job very well in the vuTreeList tool, for branches and items in each branch.
It definitely helps to see the geometry in a data tree.
