Assistant: Fix lockfile logic
Previously, Assistant was able to re-execute itself due to a quirk in the global cursor tracking logic, it seems. Now it has become necessary to explicitly drop the lockfile before activating the new Assistant instance. Alternatively, this has always been a latent bug that only now has become more likely.
This commit is contained in:
parent
dbc8465c20
commit
2f38cad987
Notes:
sideshowbarker
2024-07-18 04:27:45 +09:00
Author: https://github.com/BenWiederhake Commit: https://github.com/SerenityOS/serenity/commit/2f38cad9874 Pull-request: https://github.com/SerenityOS/serenity/pull/9881
1 changed files with 1 additions and 0 deletions
|
@ -244,6 +244,7 @@ int main(int argc, char** argv)
|
|||
text_box.on_return_pressed = [&]() {
|
||||
if (!app_state.selected_index.has_value())
|
||||
return;
|
||||
lockfile.release();
|
||||
app_state.results[app_state.selected_index.value()].activate();
|
||||
GUI::Application::the()->quit();
|
||||
};
|
||||
|
|
Loading…
Add table
Reference in a new issue