✨ Better-distinguish actions with identical frames in radial menu

Open
#1,153 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
macos, swift
Domain
design, desktop

Research direction

The issue names no files or tests. Start by locating the Cycle preview rendering and how the selected action is represented when multiple actions share a preview. Done means identical previews visibly distinguish the selected keybind, with a customizable color for the next preview, and the behavior is tested.

Written by the indexing model from the issue text.

Description

Feature
Feature Request Summary

Addition of a visual hint for actions using the same window preview in a Cycle.

Problem / Opportunity & Desired Solution

Problem:
Currently, when using keybinds/actions that show the same preview, such as “Maximize” and “Fullscreen”, the preview doesn’t visually indicate which keybind is currently selected when both actions are part of the same Cycle.

Desired solution:
A visual hint indicating which keybind within the Cycle is currently selected, i.e. by using another (customizable) color for the next preview.

Alternatives Considered

No response

Visuals or References

https://github.com/user-attachments/assets/58b8e186-1da1-4cac-879d-0ccc8bf253f4

Additional Context

No response

Priority

High (mission critical)

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.