-
-
Notifications
You must be signed in to change notification settings - Fork 213
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
Functionality to 'pin' certain copied items [Feature Request] #223
Comments
Hi @casarodante. Just use Shift-F in the bezel to save something to your favorites and just the “f” key to switch between viewing the main clipping store and favorites. |
Thanks for the response but I cannot seem to make it work with the instructions. When I click on the icon in my bar, it brings up the list that I have. Assuming that this is the bezel, a Shift-F goes in the search bar.
Any other simpler instructions for me would be great!
Thanks!
————
Roger
www.casarodante.org
…On Feb 6, 2021, 4:56 AM -0700, MarkJerde ***@***.***>, wrote:
Hi @casarodante. Just use Shift-F in the bezel to save something to your favorites and just the “f” key to switch between viewing the main clipping store and favorites.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
@casarodante Thanks to you and your question I've found this feature I didn't know it existed.
|
Oh, it’s not that complicated, but yeah the “bezel” is shift-command-v to open (and has nothing to do with the menu). Once it’s open you don’t have to keep holding anything, unless maybe having “sticky bezel” unchecked in the settings adds that sort of requirement. Just “f” and “shift-f” like I mentioned to invoke those actions. |
Oooooh so that's what sticky bezel does!! /me slaps on her forehead 🤦♀️ Thank you so much!! |
Love Flycut.
I would like the ability to pin items to the top of the list to ensure they don't drop off the list prematurely. This way frequently used items would be easier to access.
Thanks!
The text was updated successfully, but these errors were encountered: