DATABASE SELECTOR at top of wateva window - GO-AROUND

[DingBEN]

Details

Sweet and short
The way around that pesky useless database selector that one must always chase
is to make sure all queries state the database: FROM database1.table
that way if the selector is on database2 ... it saves me the constant CLONK
...as mentioned in other posts, TRASH this approach, it is cumbersome and useless, only gets in the way
[ unless you implement it appwide... I now have trashed it, will never use it and will never worry about it, no more CLONKs ]

BASICALLY all your windows are tied to a query and its database
This amounts to changing your approach and make the app QUERYcentric(data) and let a list of queries be picked from a system table to move around. ...that also takes care of queries that address multiple databases. ...a 'current' database has not much meaning.

Operating system - WIN7 Pro

SQLiteStudio version - 3.2.1