Skip to content
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

wsd: suppress Ctrl+q #10817

Merged
merged 1 commit into from
Jan 7, 2025
Merged

wsd: suppress Ctrl+q #10817

merged 1 commit into from
Jan 7, 2025

Conversation

Ashod
Copy link
Contributor

@Ashod Ashod commented Dec 28, 2024

The Ctrl+q shortcut exits Core when
forwarded. There is no use to having
this shortcut processed in Core, so
we suppress it.

If we should process it by saving and
closing the document, it needs to be
handled in a special way (ideally by
sending 'closedocument' from the
client instead).

Change-Id: I6b3280342490a013645ae73888188f20cd25168d
Signed-off-by: Ashod Nakashian [email protected]

The Ctrl+q shortcut exits Core when
forwarded. There is no use to having
this shortcut processed in Core, so
we suppress it.

If we should process it by saving and
closing the document, it needs to be
handled in a special way (ideally by
sending 'closedocument' from the
client instead).

Change-Id: I6b3280342490a013645ae73888188f20cd25168d
Signed-off-by: Ashod Nakashian <[email protected]>
@Ashod Ashod requested a review from caolanm December 28, 2024 00:48
Copy link
Contributor

@caolanm caolanm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In core this is .uno:Quit as Q_MOD1 in officecfg/registry/data/org/openoffice/Office/Accelerators.xcu. All Q_MOD1 are uno:Quit, so nothing seems to have rebound ctrl+q to something different in a specific translation so that potential problem doesn't arise.

@mmeeks mmeeks merged commit 0a55a15 into master Jan 7, 2025
14 checks passed
@mmeeks mmeeks deleted the private/ash/ctrlq branch January 7, 2025 17:47
@mmeeks
Copy link
Contributor

mmeeks commented Jan 7, 2025

Really we should kill uno:Quit in the core rather than around the edge like this - no doubt some other creative person will find a way to invoke it and loose their changes some other way otherwise ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants