Theory/Runtype Details open at the screen's top-left corner, then jump next to the editor

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

還沒有人認領這個 Issue。

評估

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

研究方向

Read the scripts/codereg/*theory.py and *runtype.py entry points to see how the details windows are started and positioned. Reproduce the behavior with the screen recording at 45–54 seconds, then check the headless test described in the issue: start a window with a given editor position and confirm its position stays fixed through the first second.

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

描述

9.0.0-beta.1, Debian 13 (GNOME, X11). Clicking Theory Details... in the Calculation Editor (ORCA) opens the window in the top-left corner of the screen, over the Organizer. The user moves the mouse there to use it; a few seconds later the window jumps to a new position next to the editor, and the user has to follow it. Seen in a screen recording (45–54 s).

Likely cause: the details windows are separate Python (wxPython) programs (scripts/codereg/*theory.py, *runtype.py). They are shown before they know where the editor is, and placed once they do.

Fix: pass the editor's position and size when the details window is started (an argument or environment variable), and create the window at its final place, centred on the editor, before it is first shown. Same for every code's Theory and Runtype Details.

Check: a headless test that starts the details window with a given editor position and reads the window's position before and after its first second; it must not move.

主要語言
C
星號
10
分支
8
平均合併
21 分鐘
30 天內合併 PR
1

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

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

FriendsofECCE/ECCE 的其他 Issue

查看 FriendsofECCE/ECCE 的全部 Issue

相似的 Issue

更多 C Issue

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

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