-
Notifications
You must be signed in to change notification settings - Fork 492
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
Ctrl+C must work even if a dialog window is open #11876
Ctrl+C must work even if a dialog window is open #11876
Conversation
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.
is this OS specific? because for me I can still never shutdown with Ctrl C #11544
It is not supposed to be OS-specific. I tested it on Windows and it seems to work for me. I can test on Linux, that is your OS, right? |
yes, debian |
@MarnixCroes Does it work if you wait until the wallet is fully loaded? I.e. outside the scope of #11544. |
I can never shutdown fluent.desktop with ctrl c (master). |
This solution doesn't close wasabi in the background. And I think it should close fully app from terminal.
|
As before, if you try to ctrl+c. than again open wallet, ctrl+c doesn't work anymore. |
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 solution works perfectly on macOs.
All comments seem unrelated to the PR, and I believe should be tackled in subsequent ones:
- As mentioned by @AlexisKv and discussed on Slack, this workflow should bypass the setting
Run Wasabi in background after closing
- It seems that there are some issues with Linux (in particular Debian?)
} | ||
|
||
public void SignalTerminate() | ||
public void SignalTerminate(bool ctrlCPressed) |
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 believe RPC stop command should also bypass the shutdown prevention. I would remove this parameter and always set result to true
. We could also rename function SignalForceTerminate
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 think you are right. I'll modify it.
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.
Pushed 432eabc
Does Run on background feature is turned off in settings? @MarnixCroes |
Run in background is turned on. |
@kiminuo So problem was not about linux, but about the "run into background option". We should fix it in another PR, as this one is effectively fixing the issue mentioned. I asked review from @wieslawsoltes, if UI changes are OK please consider #11876 (comment) and proceed to merge. |
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.
It fixes issue. Looks good.
…CtrlC-when-dialog-is-open
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.
tack 432eabc
also tested stop
RPC #11876 (comment)
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.
tACK on Win11
Fixes #11803
Alternative to #11857
Relevant read here
This PR is my take how I would approch the issue. I'm not sure if details on the UI side are OK or not. Review from somebody who understands that part of code would be very useful.
UI decoupling was not taken into account as well. If somebody wants to take over this PR, feel free to do so.
edit: It was found during review that this PR does not work when Run in background is turned on. Thanks for pointing it out.