[PoC] Session-level settings #144
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
s0600204
force-pushed
the
session_config
branch
from
ef7c19e to
8abc8e4
Compare
s0600204
force-pushed
the
session_config
branch
from
8abc8e4 to
b986e2d
Compare
s0600204
force-pushed
the
session_config
branch
from
b986e2d to
b1d1000
Compare
s0600204
force-pushed
the
session_config
branch
from
465f16e to
66f4a40
Compare
s0600204
force-pushed
the
session_config
branch
from
2ef52d9 to
4a4cf13
Compare
Accessible as the first item on the "Tools" menu.
…g easier See block comments in lisp/core/plugin.py for explanation of intent
s0600204
force-pushed
the
session_config
branch
from
8a51496 to
01ef62c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, it is only possible to define settings and preferences on a global, application-level basis.
However, there are times when a user (or a plugin developer) might wish to have certain settings for one production, and different settings for another. Instead of having to manually change them globally every time a user switches between sessions, the relevant settings should be saved into the session file.
Now, I'm not saying that every setting that is settable globally should be saved into a session file - far from it. What this PR contains is a dialog that plugin developers can add
SettingsPages to, and the states of the options contained in said pages will be saved to and restored from the current session file.What this PR does not contain is any
SettingsPages that use said dialog. Thus, although a user may find the dialog (on the "Tools" toolbar menu), and the code that loads from and saves to session files is functioning, this PR is more of a Proof of Concept (PoC) than something that is instantly usable by the user.