-
Notifications
You must be signed in to change notification settings - Fork 11
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
Last active layout #759
Last active layout #759
Conversation
Motivation: context.CommandManager.Add(
identifier: "toggle_focus_layout",
title: "Toggle focus layout",
callback: () =>
{
if (context.WorkspaceManager.ActiveWorkspace.ActiveLayoutEngine.Name == "Focus")
{
context.WorkspaceManager.ActiveWorkspace.LastActiveLayoutEngine();
}
else
{
context.WorkspaceManager.ActiveWorkspace.SetLayoutEngineFromName("Focus");
}
}
); |
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #759 +/- ##
==========================================
- Coverage 81.21% 81.12% -0.10%
==========================================
Files 191 191
Lines 10009 10011 +2
Branches 1123 1126 +3
==========================================
- Hits 8129 8121 -8
- Misses 1757 1765 +8
- Partials 123 125 +2 ☔ View full report in Codecov by Sentry. |
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.
I wasn't fully sure when we need to lock access to the properties. When you do your final review, can you double check for all the refactored methods whether we have all locks needed and/or can omit some of them?
I addressed most of the comments. Open issues:
|
75b5b71
to
69b43f2
Compare
Rebased on current main. Only the one question left about depreciating the remaining occurrence of |
Workspace
to useSetLayoutEngine
for setting the active layout engineprevLayoutEngineIndex
UpdateLayoutEngine
toCycleLayoutEngine
-- this made more sense to me, but happy to revert if this isn't consensusTrySetLayoutEngine
toSetLayoutEngineFromName
-- this made more sense to me, but happy to revert if this isn't consensus