-
Notifications
You must be signed in to change notification settings - Fork 106
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
feature: alt + grave behavior now implemented alongside alt + tick #3216
Conversation
9f85fed
to
a00a1aa
Compare
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've not yet reviewed the functionality, but there's a bunch of "housekeeping" that can be cleared away already.
void advise_new_window(WindowInfo const& app_info) override; | ||
|
||
void advise_delete_window(WindowInfo const& app_info) override; | ||
|
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.
We should document when these are introduced.
void advise_new_window(WindowInfo const& app_info) override; | |
void advise_delete_window(WindowInfo const& app_info) override; | |
/// \remark Since MirAL 5.0 | |
void advise_new_window(WindowInfo const& app_info) override; | |
/// \remark Since MirAL 5.0 | |
void advise_delete_window(WindowInfo const& app_info) override; | |
/// Check if the provided window can be selected | ||
auto can_select_window(Window const&) const -> bool; |
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.
/// Check if the provided window can be selected | |
auto can_select_window(Window const&) const -> bool; | |
/// Check if the provided window can be selected | |
/// \remark Since MirAL 5.0 | |
auto can_select_window(Window const&) const -> bool; |
src/miral/application_selector.cpp
Outdated
// If we delete the selected application, we will try to select the next available one. | ||
if (application == selected.lock()) | ||
if (*it == selected) |
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.
The code no longer agrees wit hthe comment
src/miral/symbols.map
Outdated
miral::MinimalWindowManager::advise_new_window*; | ||
non-virtual?thunk?to?miral::MinimalWindowManager::advise_new_window*; | ||
miral::MinimalWindowManager::advise_delete_window*; | ||
non-virtual?thunk?to?miral::MinimalWindowManager::advise_delete_window*; |
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.
We don't need a new stanza - we haven't released Miral 5.0 yet. (Just run the regenerate script)
…ame app multiple times in a row
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #3216 +/- ##
==========================================
+ Coverage 77.81% 77.84% +0.03%
==========================================
Files 1072 1072
Lines 75072 75154 +82
==========================================
+ Hits 58415 58503 +88
+ Misses 16657 16651 -6 ☔ 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.
This looks like a sensible implementation, and works sensibly in the scenarios I've tried.
However, there don't seem to be enough tests. I'd expect a similar number of new tests for within-app switching as we have existing tests for between-app switching. Am I missing something?
src/miral/application_selector.h
Outdated
Window active_window; | ||
Window selected; | ||
|
||
bool _is_active = false; |
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.
We don't use "_"
at the beginning of variables. (I thought the guide said something about this, but I don't see it now.) Anyway, once upon a time some library vendors assumed that the _[A-Z].+
reserved identifiers allowed macros starting with "_"
. (It is probably no longer an issue, but let's be consistent with the codebase.)
bool _is_active = false; | |
bool is_active_ = false; |
(c++)"miral::WaylandExtensions::Context::Context()@MIRAL_5.0" 5.0.0 | ||
(c++)"miral::WaylandExtensions::Context::~Context()@MIRAL_5.0" 5.0.0 |
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.
Huh?! (I can't imagine why you're adding this - it should have been there for a long time already.)
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.
When I regenerated the symbols, it got generated too
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.
Hence the "Huh?!"
@mattkae had to revert this, as it made Frame fail to start up:
EDIT: EDIT2: |
Ah that is no good! Anything I can do to help on frame's side of things? Spooky that the window was not found in the list... probably not calling a super method? |
Maybe you can track that down? |
Yup! I'll look into it now |
…ick-improved"" This reverts commit 74d847e.
Revert "Revert "Merge pull request #3216 from MirServer/feature/alt-t…
What's new?