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

UX: Desktop: Fullscreen toggle can be missed by some people and window mode not remembered

Open
  • Is something wrong?
#1,398 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
godot
Domain
desktop-dev

Research direction

Start by reviewing the desktop app's fullscreen toggle, top-right controls, options, and startup window-state handling, with Windows behavior in mind. The issue does not name files or tests. Done means the fullscreen state is discoverable, the selected windowed or fullscreen state persists, and the desktop startup behavior is decided and implemented.

Written by the indexing model from the issue text.

Description

user experience

This ticket, rather than a specific bug to fix, is more about reviewing the user experience around the window/fullscreen state of the desktop app, most notably on Windows.

The application starts fullscreen and I had a user who reported feeling a bit lost because the application did not have the taskbar or an easy way to go to other applications to take notes. They may have missed that there was a button to toggle full screen at the top right and go back to a windowed mode.

While reviewing this, I noticed also that if someone makes the application windowed, there's no setting for that actually, and next time the person starts the application, it will be full screen again.

So, I'm thinking that for discoverability, we could reflect the full screen state from the icon at the top right in the options and persist the last user selected state. And on top of that, for the desktop version, we could consider starting in windowed mode, possibly maximized or just floating window instead of full screen, just like in the browser.

Dominant language
GDScript
Stars
2.8k
Forks
236
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 GDQuest/learn-gdscript

All issues in GDQuest/learn-gdscript

Similar issues

More Desktop Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.