[Bug] Azoteq mouse button processing bug - resets the status of mouse buttons · qmk/qmk_firmware#26168

(3 留言) (0 反應) (0 負責人)C (20,368 star) (43,867 fork)batch import

bughelp wanted

描述

Describe the Bug

Hi I think there's a bug in the way mouse buttons are processed in azoteq_iqs5xx.c. It's preventing click&drag if mouse click is coming from outside of Azoteq device. It comes down to the fact that there's an empty mouse report created called temp_report and it's then being returned without consideration of previous mouse_report state. This is causing mouse button release even though user is still holding the key. I have shown this on my stream.

Thank you.

Keyboard Used

No response

Link to product page (if applicable)

No response

Operating System

All

qmk doctor Output

Is AutoHotKey / Karabiner installed

AutoHotKey (Windows)
Karabiner (macOS)

Other keyboard-related software installed

No response

Additional Context

No response

貢獻者指南

技術棧: c
領域: backend
議題類型: bug
難度: 3
預計時間: under 1 hour
活動狀態: fresh
清晰度: clear
前置要求: C programmingHID report structure
新手友善度: 80
研究方向: Investigate the azoteq iqs5xx.c file, specifically the function around line 356 where temp report is created. Understand how mouse report global state is used and why returning temp report without merging previous button states causes clicks to be released. Review the video link for a demonstration of the bug. The fix likely involves preserving the button state from mouse report into temp report before processing.