The crux with the workspace is to restore changed data that hasn't been saved so far. That is why there is a workspace database that stores the current state of all loaded data.
If QMapShack would force the user to save all data befor closing the application it would be easier. But often I change a project temporarily without the intention to save the stuff permanently. Therefore the way thru Stoney Gulch with the database. A small glossar: QMapShack configuration: That is the stuff stored in the registry (Windows), QMapShack.conf (Linux, OS X) or a file passed by -c Workspace: Everything in the top tree widget of the "Data" dock widget. Including workspace.db, which is a representation of that tree widget. Database: Everything in the bottom tree widget of the "Data" dock widget. Including the database files. The database setup is part of the configuration. The workspace isn't. Am Freitag, 12. August 2016, 09:42:35 schrieben Sie: > Hi Oliver, > > thank you for your clarifications! > > Am 11.08.2016 um 08:48 schrieb Oliver Eichler: > > Hi Wolfgang, > > > > > > the intended behavior is, that if no configuration file is given the > > registry is used. And if a configuration file is given via -c command > > line parameter the setup from the configuration file is used > > exclusively. At least with Linux it works that way. I haven't had a deep > > look on that in Windows. But I would expect it to work, too, otherwise > > Qt's implementation of QSettings is broken. But I doubt that. > > The parts of the INI file information I use (views, maps, databases, > routing, paths) work as expected. > > > The workspace database cotaining all projects loaded is a bit > > different. There is only one. Therefore it will be used by all > > configurations. Projects from databases will probe for their database > > when restored from the workspace database file. If their database does > > not exist in the current configuration, they won't be loaded. And > > therefore they won't be saved on program exit. On the next run they will > > miss. > > This explains completely the described behaviour when using different > INI configurations. My misunderstanding (or my hope) was that the > Workspace/treeWks part of the INI file might describe the projects to be > shown in the workspace. > > After looking into workspace.db with a database viewer I understand that > there is much more info about the workspace to be saved than those in > the INI. > > Have a nice weekend! > > Wolfgang Th. ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohodev2dev _______________________________________________ Qlandkartegt-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
