uclogic_exec_event_hook(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

uclogic_exec_event_hook β€” okay so bestie, here's the vibe: if the event you just received is, like, actually hooked, this function schedules the associated work. that's it, that's the whole personality ✨


πŸŽ€ SYNOPSIS πŸŽ€

bool uclogic_exec_event_hook (struct uclogic_params *p , u8 *event , int size );

like literally that's the signature, copy it exactly or the compiler WILL come for you πŸ’€


🌸 ARGUMENTS 🌸

  • p β€” the tablet interface report parameters πŸ–ŠοΈ your whole lil config situation for the report
  • event β€” the raw event, straight-up unfiltered, no edits no cap ✨
  • size β€” the size of event πŸ“ (yes, the size of the event. yes, it matters. say it with me: the size of event)

πŸ¦‹ RETURN πŸ¦‹

Returns whether the event was hooked or not β€” that's a bool, so it's giving yes/no, hooked/not-hooked, iconic binary energy πŸ‘‘


🌈 SEE ALSO 🌈

Honestly go read these next, they're the friend group:


bestie quick note: uclogic_inrange_timeout(9), uclogic_raw_event_pen(9) and uclogic_raw_event_frame(9) all live alongside this one in ./drivers/hid/hid-uclogic-core.c β€” the man page points you at the kernel file, so go look, iykyk 🫢

πŸ’… and that's the page!! πŸ’… this lil writeup came from the Kernel API Manual, lives in ./drivers/hid, and is dated October 2026 β€” the whole thing is literally titled uclogic_exec_event_hook(9) in case you forgot already 😭. mwah, go schedule some work, periodt πŸ“

πŸ“¦ where this page comes from