Skip to content
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

Using Numbers on Intel Mac #283

Open
jklock805 opened this issue Apr 29, 2023 · 2 comments
Open

Using Numbers on Intel Mac #283

jklock805 opened this issue Apr 29, 2023 · 2 comments

Comments

@jklock805
Copy link

Using Numbers on Intel Mac with OS: Vista 13.3.1

Love the product!

Problem:
In Numbers:
If a cell is selected in the spreadsheet and you command-f(ind); then paste into the find box with Flycut, the selected cell on the spreadsheet gets written over by the paste to the Find box when the find box fills with the pasted value.

It's ruining my confidence in the values on the spreadsheets.

@MarkJerde
Copy link
Collaborator

Hi @jklock805,
Numbers loses focus on the text input in the Find box whenever Numbers stops being the foreground application. You can demonstrate this by starting a find, switching to Finder or some other app, and then back to Numbers. If you try typing, Numbers doesn't accept it as input. But if you do a normal paste (without involving Flycut) it will overwrite the selected field. So there's nothing Flycut is doing that influences this. It's just how Numbers behaves.

But let's see if there's a solution that makes it at least a little bit better (and a lot less horrifying). In the Flycut bezel (Shift-Command-V or whatever you have mapped it to), you can use Fn-Return to move the selected clipping to the top of the stack (and into the pasteboard) without pasting. Doing that, you can restore a prior clipping, then Command-F to open and focus the Find box, and then Command-V to paste it into the Find box. It's a little more work, but with how Numbers behaves it hopefully will be a whole lot less stressful.

Hope this helps,
Mark

@jklock805
Copy link
Author

jklock805 commented May 1, 2023 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants