https://bugs.kde.org/show_bug.cgi?id=497653
--- Comment #11 from Finley Watson <[email protected]> --- I don't like Karl's idea of a "pseudo-TM" because the TM manager is a list of databases, not database groups. I strongly believe we should make the interface and the logic as simple as we can, and should avoid mixing ideas and meanings in the UI. I can understand defaulting to "no databases" or possibly "all databases" when selection data doesn't exist for a particular project. If a new project (and therefore a new database) is created, I can understand it NOT being added to other projects' selected databases by default. Since a project-specific database is always created and is added to as you translate its connected project, saving only the project's database as selected when there is no data makes the most sense to me. I think the above fits Valter's needs, the potential conflict is with Karl's ideas? This means: - No defaults the user can select, no separate extra "global defaults" list - Per-project selection is loaded / saved when the project is opened / closed - New project (or existing project with no selection data) defaults to only its own database selected, this info is then saved -- You are receiving this mail because: You are watching all bug changes.
