[kdevelop] [Bug 504269] [Feature Request] Ability to lock session so it cant create new ones
https://bugs.kde.org/show_bug.cgi?id=504269 Igor Kushnir changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #6 from Igor Kushnir --- (In reply to Ian H from comment #0) > Is it possible to add a locking mechanism to prevent creating a new session > when accidentally clicking it? This appears to be a rarely useful, obscure feature, which could end up confusing more often than helpful. > i will consistently click new session when i'm hitting my build button on > the toolbar. I have listed several workarounds for such accidental triggering of the Start New Session action. A more general solution is to change your system UI configuration so as not to trigger actions accidentally in any application. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 504269] [Feature Request] Ability to lock session so it cant create new ones
https://bugs.kde.org/show_bug.cgi?id=504269 --- Comment #5 from Igor Kushnir --- (In reply to Ian H from comment #4) > is it possible for kdevelop to get the session id of the one open if you > close a session and store that in the kdeveloprc file? seems to me that if > you delete a session, it probably shoulnt be remembering that deleted > session... since you clearly dont want it anymore The empty project-less session is deleted the next time KDevelop starts, so the other last-open session cannot be easily used instead. If you use only a few sessions, create separate launchers for them instead of relying on the last one being opened again. Or use the other default launcher "KDevelop (Pick Session)". -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 504269] [Feature Request] Ability to lock session so it cant create new ones
https://bugs.kde.org/show_bug.cgi?id=504269 --- Comment #4 from Ian H --- (In reply to Igor Kushnir from comment #3) > (In reply to Ian H from comment #2) > > Actual behavior: > > opens an empty session > > > > Expected behavior: > > Should open original session > SessionController::initialize() deletes unnamed sessions without projects on > KDevelop start. Without command line arguments, > SessionController::loadDefaultSession() attempts to load the last opened or > created session stored in ~/.config/kdeveloprc at [Sessions]|"Active Session > ID". If that fails, loadDefaultSession() creates a new session. The > penultimate session ID is not stored in config and therefore cannot be > opened. is it possible for kdevelop to get the session id of the one open if you close a session and store that in the kdeveloprc file? seems to me that if you delete a session, it probably shoulnt be remembering that deleted session... since you clearly dont want it anymore -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 504269] [Feature Request] Ability to lock session so it cant create new ones
https://bugs.kde.org/show_bug.cgi?id=504269 --- Comment #3 from Igor Kushnir --- (In reply to Ian H from comment #2) > Actual behavior: > opens an empty session > > Expected behavior: > Should open original session SessionController::initialize() deletes unnamed sessions without projects on KDevelop start. Without command line arguments, SessionController::loadDefaultSession() attempts to load the last opened or created session stored in ~/.config/kdeveloprc at [Sessions]|"Active Session ID". If that fails, loadDefaultSession() creates a new session. The penultimate session ID is not stored in config and therefore cannot be opened. If you always use the same session, you can create a launcher (a .desktop file) with two arguments to the kdevelop executable `-s ""` and launch it instead of the default KDevelop launcher. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 504269] [Feature Request] Ability to lock session so it cant create new ones
https://bugs.kde.org/show_bug.cgi?id=504269 --- Comment #2 from Ian H --- it's from the main menu. and actually there definitely seems to be a bug related to this. 1. Create new session 2. close new session 3. close kdevelop 4. open kdevelop Actual behavior: opens an empty session Expected behavior: Should open original session -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 504269] [Feature Request] Ability to lock session so it cant create new ones
https://bugs.kde.org/show_bug.cgi?id=504269 Igor Kushnir changed: What|Removed |Added CC||[email protected] --- Comment #1 from Igor Kushnir --- Do you accidentally trigger the Start New Session action in the main menu=>Session? Or a new session button on the same toolbar as the Build button? Toolbar actions can be edited in Settings=>Configure Toolbars... If you somehow accidentally trigger the main menu action, you could move the Build button or its entire toolbar elsewhere. Or use the shortcut (F8 by default). -- You are receiving this mail because: You are watching all bug changes.
