Skip to content

Conversation

@Jay-o-Way
Copy link
Contributor

Closes: #702, #1083
Because hotkeys can be changed while enabled.

@ChenYiLins
Copy link
Contributor

Ah, it seems that #1119 will conflict with this PR.

@Spiritreader
Copy link
Member

Ah, it seems that #1119 will conflict with this PR.

Yes, please coordinate if a combination of the PRs is possible.

@Jay-o-Way
Copy link
Contributor Author

Ah Yes. @ChenYiLins since these changes are not so big, can you copy them into your branch?

@Jay-o-Way Jay-o-Way added the do not merge Facing the developer, please don't merge this pull request label Oct 19, 2025
@Spiritreader
Copy link
Member

@ChenYiLins @Jay-o-Way Is this PR still relevant?

@ChenYiLins
Copy link
Contributor

@ChenYiLins @Jay-o-Way Is this PR still relevant?

About ThemePickerPage still makes sense. But my suggestion is that we can create a new PR. ( •̀ ω •́ )✧

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do not merge Facing the developer, please don't merge this pull request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Task] Disable settings (versus hiding) More user-friendly Hotkeys assignment User interface

3 participants