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

Add a window full-screen changed event

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
cpp
Domain
desktop

Research direction

Start by tracing Window::SetFullScreen() and IsFullScreen() on macOS, Windows, and Linux. Review the listed native notifications and window-state event, including the Windows style and title-bar restoration concerns. Done means a full-screen change event is emitted for programmatic and user-triggered changes on each platform.

Written by the indexing model from the issue text.

Description

enhancement

Window::SetFullScreen() / IsFullScreen() exist on all three desktop platforms, but there is no event when a window enters or leaves full screen. That includes changes the user triggers (the green button on macOS, F11 / the window manager on Linux). Apps that change their layout in full screen currently have to poll.

Proposal: add a WindowFullScreenChangedEvent (or an entered/left pair), emitted:

  • macOS: NSWindowDidEnterFullScreenNotification / NSWindowDidExitFullScreenNotification
  • Windows: from SetFullScreen(), which is the only way in since Win32 has no native full-screen state. Note that WM_SIZE arrives with SIZE_RESTORED, so it can't be detected from the size message.
  • Linux: window-state-event with GDK_WINDOW_STATE_FULLSCREEN

It should also be checked that the Windows SetFullScreen() restores the style and title bar correctly on exit (see leanflutter/window_manager#579 and #569).

Background:

  • leanflutter/window_manager#560: onWindowEnterFullScreen / onWindowLeaveFullScreen never fire on Windows
  • leanflutter/window_manager#559: a draft PR for Windows full-screen handling
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.