Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

SetIgnoreMouseEvents: implement on Linux and support forwarding mouse moves

Open
#67 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
cpp, linux, macos

Research direction

Start with Window::SetIgnoreMouseEvents() in src/platform/linux/window_linux.cpp and inspect the existing SetInputShape() implementation. Read leanflutter/window_manager#94 and #96 for the Linux and forwarding context. Done means the Linux stub is implemented and the requested forward behavior is addressed across the supported platforms, with the scope and platform approach resolved.

Written by the indexing model from the issue text.

Description

enhancement

Window::SetIgnoreMouseEvents():

  • is a stub on Linux (src/platform/linux/window_linux.cpp); an input shape (gdk_window_input_shape_combine_region with an empty region) would do it
  • has no forward option. Electron's setIgnoreMouseEvents(true, {forward: true}) still delivers mouse-move events while clicks pass through, so an overlay can detect hovering over its interactive parts and turn click-through off there. On macOS that's a tracking area or a global mouse monitor; on Windows, WS_EX_TRANSPARENT plus a low-level mouse hook or polling.

SetInputShape() (Linux-only so far) covers the "only these regions are clickable" case, and could be a better answer on macOS/Windows too.

Background:

  • leanflutter/window_manager#96: the forward parameter does nothing
  • leanflutter/window_manager#94: implement setIgnoreMouseEvents on Linux
Dominant language
C++
Stars
34
Forks
7
Avg merge
3d 1h
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from libnativeapi/nativeapi

All issues in libnativeapi/nativeapi

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.