SeongTae Jeong

Thanks for good suggestion. I've implemented this feature before. (#2390, #2420) However, I've confirmed that this feature doesn't work for now. I will fix it ASAP. > It is verified...

@uvtofu That's a good point. So, what do you think about design a 'configuration.ini' file to be loaded if it exists? If there's no disagreement, I'll start the code this...

@uvtofu If so, how about the DB4S to load the 'sqlitebrowser.conf' file if it exists in the 'config' directory?

I made a PR by code that can solve this issue. It will be reflected in the 'master' branch after code review. That PR make DB4S will load settings if...

I also agree with @mgrojo. To add a bit more comments, I think it would be better if the installer creates a shortcut to the executable file containing the command...

DB4S has the advantage of having fewer condition comparison commands when creating shortcuts that contain the portable installer command line. (Of course, the overhead given by this condition is not...

@mgrojo, @MKleusberg I created this PR and enlisted in the military for about 2 years according to my civic duty, and I was recently discharged. I'm really sorry for the...

@chrisjlocke Even if there is a configuration file, command-line option is take precedence. but as pointed out, there is no warning output. I will fix it. Thanks for advice! 😄...

@chrisjlocke It looks like we need to add the generated token to our repository Action Secrets before merge this PR :) [Settings -> Security -> Secrets -> Actions](https://github.com/sqlitebrowser/sqlitebrowser/settings/secrets/actions) More information...

The SQLite version output by DB4S is determined at compile time, not at execution time. (see code below) https://github.com/sqlitebrowser/sqlitebrowser/blob/a78dd0292f7e1149b4e81a3987531aa67098b92c/src/sqlitedb.cpp#L543 >The constant SQLITE_VERSION value is in your installed SQLite library code...