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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make Global and Profile settings inheritable #7923
Make Global and Profile settings inheritable #7923
Changes from 8 commits
62b2a90
570afa2
374ad80
ae97064
cb59ec1
d1ddab5
2866b4e
d74f236
9685108
298636b
49b98b3
e026f32
dd8a2cb
07351bb
6d34980
6e1849b
80e234b
7150e52
0a806fd
401efb8
1292633
0c549f0
5c594f3
01e2c49
e0e3943
b4ec4da
2716fa0
36211ba
b55856e
6f55ae5
4cf3b1c
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, to get this right, every node in the GlobalAppSettings inheritance graph has a full copy of the parent's schemes and commands, correct? So for these, we can't really tell what layer a command was actually defined at, right? But there's no other way of doing this, because we can't easily express "Layer 2 undefined {command} from layer 1", right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor thing I messed up. These should be
std::move
instead of copies. That way we don't hold on to an extra copy of color schemes, commands, etc. that we'll never touch. So instead we'll just have one copy of all of this and pass it down to the leaf.Exactly. This goes back to the discussion we were having about doing action IDs sooner than later. With action IDs, we should be able to layer an action onto our ancestors. Additionally, we'll have to design our own data structure solution that...
while also maintaining more complex functionality like "unbind" and "rebind" a command. These two work items are pretty intertwined IMO.