Jump to content

Strange Challenge with some Key Combo Dispatches


Recommended Posts

23-Apr-24 - Update: It seems to be any key combo with left, right, up or down in it

 

I have created a simple workflow to help me remember a couple of shortcuts

 

They all seem to work except for:

 

⌃ ⎇ ←

⌃ ⎇ →

 

There does not seem to be any issue with the way it is setup and I see the dispatchers being called when the debugger is running

 

I have confirmed that there are no conflicts, and these shortcuts are indeed functional. (I even tried these with BTT and BTT has no issue in dispatching them)

 

Could anyone provide me with some guidance, or could this possibly be a bug?

 

image.png.1278682b3046ff99e91b8ea5578a98cb.png

Edited by gregzacola
Update
Link to comment

All seems to be fine:

[Dispatch Key Combo] Interpreted '⌃⌥→' as '→' with mod code 9175040 (using code 124)

 

Using the ability for the key combo to accept a string, you can see if even interprets the arrow correct as 124 which is dead on

 

I'm at a loss :(

Link to comment

I've now resorted to a workflow that calls an apple shortcut to achieve this

 

The only issue is that something that should be fast now has the added delay of calling the shortcut

 

If anyone has any ideas on the cause of this issue, please let me know

Link to comment

@Andrew i know this isn't in the bug forum but I was able to reproduce @gregzacola's issue. It appears using arrow keys in the arrow cluster don't appear to dispatch properly. I didn't set up that elaborate list filter (which is a cool way to learn some shortcuts), but did set up a simple keyword to trigger the keycombo. I then assigned it to an action in moom. If I use modifiers with any other key it will work, but if I assign modifiers to something in the arrow cluster it won't. Is this by design for some reason or a bug?

Link to comment
  • 1 month later...

Hi @Andrew - I'm experiencing the same with function keys

 

e.g. 

 

`[Dispatch Key Combo] Interpreted '⌃⌥⇧F4' as 'F4' with mod code 9306112 (using code 118)`

 

Any ETA on the fix for the issue reported in April?

 

Thanks

Link to comment
6 hours ago, gregzacola said:

Any ETA on the fix for the issue reported in April?

 

As I said, this is being tracked internally. I can't share ETAs for individual issues and features.

 

Cheers,

Andrew

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...