✨ Allow existing Custom keybinds to be added to Cycles

Open
  • Is something wrong?
#1,152 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
macos, swift
Domain
desktop

Research direction

Start by locating the Cycle menu entry point and the saved Custom keybind model or selection flow. Check how a Cycle currently stores a Custom item, then verify that selecting an existing keybind preserves its link so later Custom keybind changes appear in the Cycle; add or update relevant tests if the project has them.

Written by the indexing model from the issue text.

Description

Feature
Feature Request Summary

Option to add Custom (saved) keybinds to Cycles.

Problem / Opportunity & Desired Solution

Problem:
When creating a Cycle, it’s currently not possible to select existing Custom keybinds. Instead, they have to be recreated within the Cycle menu by adding a Custom item and configuring it again.
I have quite a few Custom keybinds that I’d like to experiment with in my radial menu, and I may also change them from time to time. Having to recreate each Custom keybind every time I want to add it to a Cycle is a bit cumbersome.

Desired implementation:
It would be more convenient if existing Custom keybinds could be selected directly within the Cycle menu. This would also mean that changes made to a Custom keybind would automatically carry over to any Cycles using that keybind.

Alternatives Considered

Manually recreating each Custom keybind within each Cycle menu. This feels like an unnecessary detour when the keybind is already saved within Loop.

Visuals or References
Image Image
Additional Context

No response

Priority

Medium (important but not blocking)

Final Checks
  • My issue is written in English.
  • My issue title is descriptive.
  • This is a single feature request (multiple feature requests should be reported individually).
  • I have looked to see if this is a duplicate of another feature request.
  • I can help with research or testing.
  • I can help code this feature.
Dominant language
Swift
Stars
11.9k
Forks
287
Avg merge
17h 7m
Merged PRs (30d)
5

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mrkai77/Loop

All issues in mrkai77/Loop

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.