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 workspace database containing 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. HTH Oliver Am 10.08.2016 um 19:36 schrieb Wolfgang Thämelt: > The QMS Windows version seems to save information about the state of the > workspace at 2 (?) locations > - in the registry, > - if used in an INI-file (the workspace part looks very similar to the > registry one). > > When working with different INI-files including different databases the > following problem comes up: > > - Start QMS with INI-file 1 and database 1, select some items for the > workspace, close QMS. > At the end of the run both the registry and the INI-files are updated. > > - Start QMS with INI-file 2 and database 2, select some items for the > workspace, close QMS. > At the end of the run both the registry and the INI-files are updated. > > - Restart QMS with INI-file 1. Then the workspace saved in the first > step is not reestablished. > Either the INI file 1 doesn't keep the workspace state or the > registry info overwrites the INI info. > > Would it be possible to give some hint how to save properly the > workspace state for further use in the described situation? Is this a > precedence problem (registry info wins and not INI info)? > > Thanks for help > > 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 ------------------------------------------------------------------------------ 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
