Shortcut keys have no effect on strip when VSEQF is enabled unless the mouse is moved first

[kodiakcreativity]

This has been an issue for a while, I don't have specific version numbers. but I just recently attributed it to VSE quick functions, disabling the add-on fixes the issue, but the add-on is so useful I don't want to live without it!

behaviors observed. I'm going to use move (g) as an example, but I see the same behavior on just about any shortcut key.
start with the strip unselected, click the strip to select it and press g. nothing happens. the strip does not go into move mode.
to get around the problem I find you must interact with the mouse before clicking g. if you click a second time, or move the mouse (within or out of the strip doesn't matter) the g key then works.

this behavior I see is consistent, there are never situations in which this doesn't happen. if I turn VSEQF off, this problem fixes itself, you can click on a strip, press g, and simply move it as expected. turn VSEQF back on, the bug returns.

this works the same way for all kinds of strips, video, audio, modifiers etc. it also affects the strip end handles in the same way. it affects almost all keyboard shortcuts not just move. for example if I try to add a modifier to a strip, click the strip press SHIFT+A, nothing happens. if I select the strip, then move the mouse (even a little) press SHIFT+A the context menu appears like normal.

one more note, the shortcut keys continue to be disabled until the mouse moves, meaning:
select a strip then take your hand off the mouse so it does not and has not moved.
press any short cut key or combination of keys as many times as you want, none of them have any effect.
move the mouse,
repeat the above, the shortcuts all work again.

This may seem like such a small issue, but I encounter this problem constantly when using the VSE, apparently the way I work the computer I click on a strip and attempt to use shortcut keys right away without moving the mouse at all, while VSEQF is enabled, it causes those keys to have no effect.

I have updated to the latest version of VSEQF, this is blender 3.0 on Ubuntu 18.04. the problem existed for the last several releases of blender and VSEQF at least.
I also tried to turn off all VSEQF features that I don't routinely use to see if its a problem with any function in particular. auto parenting, quick markers, quick tags, quick cuts, compact edit panel, quick three point etc all turned off. the behavior still exists.

[Bardoctorus]

Apologies if this isn't the right way to double up on a report, but I'm facing the exact same issue, Linux Mint 20.2 Cinnamon. Also confirmed that turning the add-on off fixes it. Much like kodiak above, I'm just muddling through as the add-on is so useful!

[snuq]

Im sorry, i really dont know whats going on... i cant reproduce this, in blender 2.93 or 3.0.1 (tho, im on windows). Are there any error messages in the console, either on start up or when pressing a shortcut?

[Bardoctorus]

Hmmm, I wonder if this is a Windows Linux thing then. I work on Windows too, though I get Adobe through my work so never tried Blender VSE - I'll spool it up later and see if I can replicate it. I'll try to get some screengrabs/logs on my Linux machine when I get the chance!

edit: a word

[asbestosbill]

I'm on Windows, using 3.2a, and I experience this too. Click on a sequence, hit G or K, and nothing happens; move the mouse slightly, then G and K work as expected.

[snuq]

It seems that this only happens when in left-click mode, I can reproduce it when I set that mode. Also, probably related, sometimes parenting doesn't activate when left-click-dragging it seems. I'll have to do some digging, but at least I know WHERE to dig now.

[snuq]

Seems that blender's 'Tweak' tool is eating the inputs somehow... if you change the tool mode to select box, it seems to temporarily fix both of those issues. Probably the actual solution here is to add the vseqf grab as its own tool, ill have to do some research on that.

[snuq]

Added a disable for the default shortcuts that should hopefully fix this issue. This may require disabling and re-enabling the addon.
I am a little concerned Blender might decide to re-enable those shortcuts somehow, please comment if this happens and ill look into being a bit more aggressive with the disabling.