-
-
Notifications
You must be signed in to change notification settings - Fork 767
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
Repeated commands: Select which sizes to cycle between on repeated half actions #1434
Repeated commands: Select which sizes to cycle between on repeated half actions #1434
Conversation
Toggle cycle sizes stack view based on which repeated action is selected
Provide localization for Norwegian and Swedish
Thanks! I haven't had a chance to dig through this yet, but the concept makes sense to me.
|
Alright, sorry for the delay. Excellent work! All of the code changes look good to me, and I tested this out and I like it. There's a few things to iron out.
|
Remove cycle sizes options text field
Refactor Change CycleSizeDefault key to `selectedCycleSizes` Change cycleSizesIsChanges key to `cycleSizesIsChanged`
No worries about the delay. Thank you for your feedback—I like your way of thinking.
I have committed these changes, and also:
Please let me know what you think. |
Perfect! |
What a great addition ❤️ - awesome work @Eskils 👍 |
Aim
As people use a variety of screen sizes, it is desirable to cycle between different window sizes instead of / in addition to ½, ⅔ and ⅓.
Example use cases:
Changes
cycleBetweenDivisions
andcycleBetweenDivisionsIsChanged
.Changes to Settings View in Storyboard
These changes are mainly made to accommodate animation of toggling the cycle sizes view and the Todo-mode view.
Detaches Hidden Views
set to false.This attached video shows the changes in action:
RectangleCycleBetweenSizesDemo.mp4
Considerations
In the old implementation, the user default
altThirdCycle
was used to change the order of the second/third cycle. I can however not find any setting for it, nor any other references to it in the code apart from it being declared in Defaults.swift. Is it okay to ignore this property? Should it be removed, or should I adapt my implementation to take it into account?I have added one string, and changed one string. What are the procedures on how these are localized?
I hope you will consider my proposal.
Please let me know if there is anything I should change or do differently.