joelekstrom / fastmate

A native Fastmail-wrapper for Mac.
MIT License
194 stars 12 forks source link

⌘N (New mail) and ⌘F (Find) not working? #2

Closed pro-sumer closed 6 years ago

pro-sumer commented 6 years ago

Both ⌘N (New mail) and ⌘F (Find) are not working for me.

Expected results:

Actual results:

joelekstrom commented 6 years ago

Interesting! This works fine for me. I'll need some additional info:

What OS version are you running?

What view are you in when trying the shortcuts? It only works when you're in mail, and not settings or calendar for example.

pro-sumer commented 6 years ago
joelekstrom commented 6 years ago

I figured it out. The shortcuts stop working when the sidebar is hidden, even if it’s enabled again.

I’ll try to fix it later today!

joelekstrom commented 6 years ago

Hey again, here's a beta that should fix the ⌘N-shortcut. Can you verify that it works?

I haven't figured out a way to improve the ⌘F-shortcut, however, that one seems to always work for me. Can you verify that you still have a problem with ⌘F in this beta version?

Fastmate.zip

pro-sumer commented 6 years ago

Yes, both ⌘N and ⌘F are working now in the FastMail production interface.

PS: Tested via building after commit aeb9777 (instead of running your binary)

pro-sumer commented 6 years ago

Now both are not working again... Trying to figure out why.

Observation:

(don't have an external keyboard available right now to verify)

pro-sumer commented 6 years ago

Unfortunately that assumption turns out to be incorrect:

Both ⌘N and ⌘F are not working now (no matter whether I try the external or internal keyboard).

pro-sumer commented 6 years ago

Sorry, apparently I was testing with the FastMail beta interface today...

Both ⌘N and ⌘F are working (with the external and the internal keyboard) on the production interface.

joelekstrom commented 6 years ago

Cool! I should check out the beta interface and make sure Fastmate works with it. Thanks for letting me know about it. I'll submit a new version with the fixes for now.

joelekstrom commented 6 years ago

Fixed in v1.0.3