Repository navigation
Row height is not kept if the values from a column is sorted #2006
Description
Details for the issue
What did you do?
I sorted a column.
What did you expect to see?
The height of the rows to be kept.
What did you see instead?
The height of the rows are not kept.
Useful extra information
The info below often helps, please fill it out if you're able to. :)
What operating system are you using?
- [ X ] Windows: ( 10 )
What is your DB4S version?
- 3.11.2
Did you also
- Try out the latest nightly version: https://github.com/sqlitebrowser/sqlitebrowser#nightly-builds
Activity
chrisjlocke commentedon Sep 24, 2019
Why would row heights be kept? Usually, the grid would be cleared, clearing all rows, thus 'starting again'. When you sort on a column, the rows aren't shuffled around into the new order.
I don't think this is something that we could do much for. We could note row heights before sorting, but row 1 now might be on page 2. A row on page 3 (which we haven't seen yet) is now on page 1 - do we set a default height?
I don't think is a bug per se, but more of a feature request?
silviulaurentiu commentedon Sep 24, 2019
Thank you for your response :-)
If you want, you can consider a feature request.
The idea is to use this feature also with the image thumbnails: #2000
I think the easiest way to use this, is to have an option for this (a check box - for example, for auto-height of rows), and if this is checked, then after the sorting of a column, or when the page is changed (a new page is requeste, for example), all rows from current page to be auto-height.
Thank you very much!
Enhancements in row and column resizing to fit contents
mgrojo commentedon Dec 21, 2019
@silviulaurentiu The next nightly build will have an option in the contextual menu of the row header, which will set the rows to auto-height. I think this will be useful for your case of embedded thumbnails or for tables containing long texts.
Beware that activating it on large tables will severely delay the display of data.
Could you give it a try and report any flaw. If it is working well, it could be added to project files as a setting per table or per DB.
SilvioGrosso commentedon Dec 23, 2019
@mgrojo
Just tested on Windows 10.
It works fine!
The problem with images is that, right now, they slooow down the software a loooot :-) :-)
Even when they are compressed (jpeg) they take a huge toll on performances (scrolling stuff).
I suppose this feature should be proposed as "optional" until the code is optimized for speed.
See comment by @MKleusberg on bug: #2000
Allow activating "Adjust rows" in views