You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hmmm, I think we've done some work with that already recently. Which OS are you on? If it's Windows, would you be ok to try the latest nightly build and see if that's better for you? 😄
(download locations are listed on the front page of our repo, if that helps)
That version number sounds like a release one, @justinclift was suggesting you look at the latest nightly build. If you go to https://github.com/sqlitebrowser/sqlitebrowser and scroll down you will find some explanation and a link to the nightly build. Try that and see.
Now using 3.7.99 and I see many NEW options for changing the font and font size - but none for the row height. Even when I use a very small font size the row height remains unchanged, and too big.
I think what Justin remembered here is the new font size option which also affects the row height - one row is automatically resized to fit one line of text. Before just adding one more option I'd be curious to know what you want to achieve and if there's a way to avoid this option altogether. If there is a way to make it work out-of-the-box that's always better than making you reconfigure the whole thing, I think 😃
I tried a smaller font size, just to see if that would reduce the row height. Nope.
I want to have shorter row heights - primarily to see more rows on a single screen.
A friendly +1 for this.
I just updated from 2.0b1 to 3.9.1, I was very excited by all the progress… but then I became very sad when I saw how bigger the rows have become…
@bobatwhidbey, @vlakoff Can you try tomorrow's nightly build? I've tried adding some code in there that should help calculating a decent row height depending on the font size. Prior to this the default row height would be set by Qt to some value that might be platform dependent (= hard to predict). So maybe this already helps with your problem. If it doesn't can you include a screenshot of how it looks now vs. how you want it to look like?
Personally I'd prefer even narrower rows, like in the "Database Structure" tab. But it's highly subjective, I use quite denser layouts than most people do.
Hi Justin,
While I recently got a Win64 PC, I also have my old Win32 PC. I tried both 2017-04-11 versions (what is the difference? what is sqlcipher? ) on the Win32 PC and both worked really well. There are certainly many more features now which are not apparent how to use. I'm sure the online Help will follow.
I thought there was going to be something under Preferences that specifically addressed row height. Changing the browser font size will change the row height indirectly but I saw nothing that would change the row height directly. For example, a smaller row height with no change in font size would reduce the white space between each line.
One minor change I noticed. File names in the new version use forward slashes / instead of back slashes \ . It just looks unusual to see some of the files with back slashes and some with forward slashes when I view the most recent files in the Files menu. I think the Windows default is back slashes, although I believe either will work. As a PC user, this is something I've never paid much attention to.
Bob
The forward/backslashes thing has been around a while ... I raised it sometime ago! (#735). Other operating systems (which the main programming dudes here use - Linux, OSX, chalkboards, etc) use forward slashes, so us Windows users have to suffer! ;)
SQLCipher is used for encryption support. At the moment, someone could open your database in something like Notepad and view the data. It wouldn't be totally human-readable, but it would be 'enough'. Certainly not good enough if you were storing usernames and passwords, and everyone had access to the database. For small application use (the main use of SQLite?) or if encryption isn't important, you can ignore the SQLCipher option. :)
@bobatwhidbey As an update, the backward/forward slash inconsistency is fixed in nightly builds from just over a week ago. We haven't added the row height option (yet) though, but will probably get around to it "at some point". 😉
Activity
justinclift commentedon Sep 29, 2015
Hmmm, I think we've done some work with that already recently. Which OS are you on? If it's Windows, would you be ok to try the latest nightly build and see if that's better for you? 😄
(download locations are listed on the front page of our repo, if that helps)
bobatwhidbey commentedon Sep 29, 2015
I'm on Win7. I'm leaving today for the week but will be back on Sunday. I would be happy to test at that time.
justinclift commentedon Sep 29, 2015
Sure, no worries at all. 😄
bobatwhidbey commentedon Oct 3, 2015
Hi Clift,
I have version 3.7.0 installed on a Win-32, Win7 PC. I don't see
where I can change the row height size.
Bob
glawrence commentedon Oct 4, 2015
That version number sounds like a release one, @justinclift was suggesting you look at the latest nightly build. If you go to https://github.com/sqlitebrowser/sqlitebrowser and scroll down you will find some explanation and a link to the nightly build. Try that and see.
bobatwhidbey commentedon Oct 4, 2015
Now using 3.7.99 and I see many NEW options for changing the font and font size - but none for the row height. Even when I use a very small font size the row height remains unchanged, and too big.
MKleusberg commentedon Oct 5, 2015
I think what Justin remembered here is the new font size option which also affects the row height - one row is automatically resized to fit one line of text. Before just adding one more option I'd be curious to know what you want to achieve and if there's a way to avoid this option altogether. If there is a way to make it work out-of-the-box that's always better than making you reconfigure the whole thing, I think 😃
bobatwhidbey commentedon Oct 5, 2015
I tried a smaller font size, just to see if that would reduce the row height. Nope.
I want to have shorter row heights - primarily to see more rows on a single screen.
justinclift commentedon Oct 9, 2015
Makes sense. @MKleusberg What do you reckon? Do-able?
vlakoff commentedon Apr 9, 2017
A friendly +1 for this.
I just updated from 2.0b1 to 3.9.1, I was very excited by all the progress… but then I became very sad when I saw how bigger the rows have become…
Try setting a saner default row height in the data browser
MKleusberg commentedon Apr 10, 2017
@bobatwhidbey, @vlakoff Can you try tomorrow's nightly build? I've tried adding some code in there that should help calculating a decent row height depending on the font size. Prior to this the default row height would be set by Qt to some value that might be platform dependent (= hard to predict). So maybe this already helps with your problem. If it doesn't can you include a screenshot of how it looks now vs. how you want it to look like?
vlakoff commentedon Apr 11, 2017
Yes, there is an improvement. Here are some screenshots:
Personally I'd prefer even narrower rows, like in the "Database Structure" tab. But it's highly subjective, I use quite denser layouts than most people do.
So, it should be fine as it is now. Thanks!
justinclift commentedon Apr 11, 2017
@vlakoff Awesome. 😄
@bobatwhidbey Do you have the time/interest to try the latest nightly build, and see if that's better for you? 😄
If so, and if you're still using Win32, the latest nightly builds are here:
https://nightlies.sqlitebrowser.org/win32/
bobatwhidbey commentedon Apr 11, 2017
chrisjlocke commentedon Apr 11, 2017
The forward/backslashes thing has been around a while ... I raised it sometime ago! (#735). Other operating systems (which the main programming dudes here use - Linux, OSX, chalkboards, etc) use forward slashes, so us Windows users have to suffer! ;)
SQLCipher is used for encryption support. At the moment, someone could open your database in something like Notepad and view the data. It wouldn't be totally human-readable, but it would be 'enough'. Certainly not good enough if you were storing usernames and passwords, and everyone had access to the database. For small application use (the main use of SQLite?) or if encryption isn't important, you can ignore the SQLCipher option. :)
justinclift commentedon May 17, 2017
@bobatwhidbey As an update, the backward/forward slash inconsistency is fixed in nightly builds from just over a week ago. We haven't added the row height option (yet) though, but will probably get around to it "at some point". 😉