Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

SetAspectRatio should constrain the content area consistently across platforms

已關閉
#64 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
48/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
cpp
領域
desktop

研究方向

Start at Window::SetAspectRatio and trace the platform-specific implementations, especially Windows WM_SIZING and programmatic resize handling, alongside Linux geometry hints and macOS contentAspectRatio. Done means the Flutter content area, rather than the whole window including non-client decorations, maintains the requested aspect ratio consistently across platforms.

由索引模型根據 Issue 內容生成。

描述

bug

Window::SetAspectRatio() behaves differently per platform:

  • macOS constrains the content area (contentAspectRatio), unless the content is full-size.
  • Windows constrains the whole window rect in WM_SIZING, title bar and borders included, so the Flutter view ends up with a different ratio.
  • Linux uses geometry hints on the window, and users report the content not matching the ratio.

Expected: the ratio applies to the content area on all platforms. On Windows, subtract the non-client size before applying the ratio in WM_SIZING, and apply it to programmatic resizes too.

Background:

  • leanflutter/window_manager#437: exclude the title bar from the aspect-ratio calculation
  • leanflutter/window_manager#520: actual window ratio differs from the one set
  • leanflutter/window_manager#566: setAspectRatio behaves differently on Windows and Linux
主要語言
C++
星號
34
分支
7
平均合併
3 天 1 小時
30 天內合併 PR
1

貢獻指南

這個儲存庫沒有索引到貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

libnativeapi/nativeapi 的其他 Issue

查看 libnativeapi/nativeapi 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。