✨ Custom Action changes

Open
  • Is something wrong?
#985 2 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
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
macos, swift
Domain
desktop

Research direction

No files or tests are named. Start by locating the existing Custom Action grow/shrink and move entry points, then inspect how slider values are displayed and serialized to JSON; done means directional changes work and slider integers coexist with precise decimal text values.

Written by the indexing model from the issue text.

Description

Feature
Feature Request Summary
  • Add Grow/Shrink option that can grow/shrink in multiple directions (left + up, right + down, etc) instead of using a size and/or position
  • Add Move option that can move in multiple directions instead of using a position and/or size
  • Truncate precise pixel/percent values — seeing 33% in the menu and 33.381209002 in the json is not great. Add visual support for decimal values from using the text box and only use integer values from the slider
Problem / Opportunity & Desired Solution

The current grow/shrink options are limited and slow sometimes when trying to make a window significantly different sizes without spamming a keybind. They also limit modularity, where you could have a keybind just reduce or increase the size of a window by a third of your screen size horizontally instead of having multiple bindings for each third and each sixth of your screen.
Movement options are also slow and don't allow moving across screens into possibly specific positions really fast.
The floating point values not being displayed on all of the sliders also keeps the experience from being clean, where thirds, sixths, and ninths as sizes are inconsistent and may overlap or be too small. editing json to get proper values is not fun.

Alternatives Considered

I think these all fit as one single request because they should all be added in tandem or ignored altogether. While yes these are pretty niche changes, that's the beauty of this app — there's already a lot of niche movements and modular changes.

Visuals or References

No response

Additional Context

No response

Priority

Low (nice to have)

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.