[Bug] Unexpected behaviour change since v1.8.1 (currently using v1. 11.2

[laundmo]

Description

In v1.8.1, when Paint-to-Span was added, setting the paint-to-span keybind would allow using only that keybind to start zones + paint to span. FancyZones didn't work like this, but I ended up liking it a lot - i can just use one key to both start PlasmaZones snap and paint.

When i updated today, PlasmaZones updated as well, changing this behaviour

I know that the current behaviour is likely intended, but as i said, even in the short few days i've come to really like the wholly separate buttons for just snap, or paint-to-span. Maybe this should've been a feature request, but by the time i thought of that i'd already written it as a bug report...

Expected Behavior

Expected the Paint-to-Span keybind to work without the zone activation keybind.

Steps to Reproduce

1. Set Zone activation keybind to Shift
2. Set Pain-to-Span keybind to Ctrl
3. Grab a window
4. Hold Ctrl
5. PlasmaZones doesn't show up

PlasmaZones Version

v1.11.2

Display Server

Wayland

Desktop Environment

Plasma 6.5.5

Distribution

EndeavourOS with CachyOS repos

Relevant Logs

No response

Configuration

No response

Checklist

• I searched existing discussions and issues
• I can reproduce this with default settings

[fuddlesworth]

Hmm. This was actually a bug in the code. Zone Span and Snap Assist were triggering with their own keybinds and it was meant to be while overlay was active.

Maybe I can make a new option for Zone Span and Snap Assist to be triggered outside of the overlay.