Description: Add a capability that will allow selection of any column for viewing its data while scrolling up/down instead of the row number. For example, right click on the scroll area or any component used in scrolling and select a column to view. Could also be setup through a "scroll" selection in the View pulldown. Actual Results: Can only see row number now Expected Results: Would like to be able to select any column for viewing Reproducible: Always User Profile Reset: No Additional Info: see above
Please describe in more detail: 1. How do you arrive in a situation where you only see the row number, but not the column identifier 2. What you mean by selection of any column for viewing
1. On the vertical scroll bar, click on the thumb and drag up or down and the row number will be displayed in a box adjacent to the thumb. Instead of the row number , I would like to see the content of a preselected column at that row number. For example: A B C 11 dog 12 cat 13 bird 14 mouse Now when dragging the thumb up/down I will see row # 11, 12, 13, 14 in the box adjacent to the thumb. I would like to be able to see the data in col B when dragging the thumb. When thumb at row 11 the box showed 11, would like to be able to show "dog", at row 12 show "cat" ... This requires that somewhere there needs to be a capability in calc to switch from the displaying the row number to displaying the content of the user selected column at that row number
In case this helps in understanding the request... s/(popup) box/tooltip widget
(In reply to ady from comment #3) > In case this helps in understanding the request... > > s/(popup) box/tooltip widget Ok, so currently on some UIs (but not all of them) we can see a tooltip with either the row or column number that is at the start of the visible area. So the request is somewhat similar, but seems to go much further, asking for a way to define like a locked selection for viewing. A mockup sketch would be very useful, but let's add UX team in case they get inspired. The summary should be changed once it is determined what this request is exactly.
(In reply to Buovjaga from comment #4) > > s/(popup) box/tooltip widget > asking for a way to define like a locked selection for viewing. Or... instead of having to select a specific column in order to show the contents of each cell while the scrollbar is being dragged, the request could be to show the tooltip with the content if the "first" column shown on the main area (whether the "first" column on display is column A, or B, or whichever). Whichever the case, please be aware that having the content of whichever cell is shown at the "home" position would not always be desirable for every user and in every situation. Moreover, some users would still like to have the current "Row #" tooltip only, without any other changing-size information (IOW, it could be distracting). To be clear, I am just trying to help towards formulating a clear potentially-useful request (for some cases/users). Whether it is implemented, or with which priority level, that's another thing.
Here is a use case: I have a spreadsheet that contains test data. Column A - test name, Column B - test date, Column C - test time, Column D... data. The sheet contains thousands of lines. I would sort on Column A (test name) and there may be 100 rows of TestA, 200 rows of TestB,... If I could set the tooltip to display column A I could easily scroll down to where TestB begins or TestX which could be several 1000 rows away. I know I can auto filter for testA but I do a lot of back and forth.
(In reply to jbuckler1016 from comment #0) > allow selection of any column for viewing its data while scrolling up/down Sounds to me as if you are looking for Freeze Row/Col or the split window function. (In reply to jbuckler1016 from comment #6) > I would sort on Column A (test name) and there may be 100 rows of TestA, > 200 rows of TestB,... easily scroll down to where TestB begins or TestX That's something different. How about a command that jumps to the next cell with different content similar to ctrl+arrow for To Left/Lower Block Margin?
(In reply to Heiko Tietze from comment #7) > (In reply to jbuckler1016 from comment #0) > > allow selection of any column for viewing its data while scrolling up/down > Sounds to me as if you are looking for Freeze Row/Col or the split window > function. @Heiko, Not at all. As described, click and hold the mouse on the vertical scrollbar, and drag the vertical scrollbar down; you should see a tooltip showing "Row #" according to the row address for the "home" location. Now re-read the request. > > (In reply to jbuckler1016 from comment #6) > > I would sort on Column A (test name) and there may be 100 rows of TestA, > > 200 rows of TestB,... easily scroll down to where TestB begins or TestX > That's something different. How about a command that jumps to the next cell > with different content similar to ctrl+arrow for To Left/Lower Block Margin? While that might help users, please remember that Calc is not really a database tool, and that this enhancement request is about a different feature.
(In reply to ady from comment #8) > (In reply to Heiko Tietze from comment #7) > > (In reply to jbuckler1016 from comment #0) > > > allow selection of any column for viewing its data while scrolling up/down > > Sounds to me as if you are looking for Freeze Row/Col or the split window > > function. > > @Heiko, Not at all. > > As described, click and hold the mouse on the vertical scrollbar, and drag > the vertical scrollbar down; you should see a tooltip showing "Row #" > according to the row address for the "home" location. Now re-read the > request. As a note, if Heiko is using KDE, he will not see these tooltips.
We discussed the topic in the design meeting. First of all there is no no compelling use case. The only idea is probably to focus some column/cell that will be out of view and you can see the content from Z1:100 on scroll while at the same time A1:100 is shown in the tooltip. For this purpose we have the freeze function, you can split the view, and hide columns. Plenty of ways to achieve the goal. Last but not least the envisioned solution would be quite hackish and not obvious how to handle for average users. And finally it wont work with all OS/DE. So the verdict is to reject the idea.