Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork7.9k
Factor out common parts of qt and macos interrupt handling.#27285
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Uh oh!
There was an error while loading.Please reload this page.
Note that we don't actually need to disable the QSocketNotifier at theend, just letting it go out of scope should be sufficient as itsdestructor also does that (see qsocketnotifier.cpp).
Thanks, fixed the copy editing. Also switched to putting the contextmanager in backend_bases, as that seems more specific than dumping it in cbook as a "general" utility. |
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.
Anyone can merge on green.
Good that you moved fromcbook
. Was about to suggest that.
Uh oh!
There was an error while loading.Please reload this page.
Note that we don't actually need to disable the QSocketNotifier at the end, just letting it go out of scope should be sufficient as its destructor also does that (see qsocketnotifier.cpp in the qt source tree).
Followup to#27221.
(Also had to rename some local variables named "signal" in the CallbackRegistry implementation; otherwise the style checker complains about shadowing the imported module name... though#26013 would make some of these irrelevant.)Switched to putting the contextmanager in backend_bases.PR summary
PR checklist