Viewer under XWayland: MO Diagram window opens black; bottom strip blinks on property switches
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 43/100
Research direction
Start by tracing the MO Diagram window creation and the property-switch path that calls wxAuiManager::Update(), then reproduce both artefacts on GNOME Wayland under XWayland with the scripted clicks and window grabs described in the issue. Compare approaches that avoid unnecessary pane updates or reuse/dock the floating window; done means neither the initial black window nor the blinking bottom strip appears.
Written by the indexing model from the issue text.
Description
Two short redraw artefacts remain on GNOME Wayland (ECCE on XWayland, NVIDIA 550), both measured on the affected desktop with scripted clicks and window grabs:
- MO Diagram window black on first opening. The floating window is black for about 100–200 ms after it appears (grabs at 11, 51 and 89 ms black, content from about 180 ms). Building the diagram after the window had painted (CallAfter) and keeping the window transparent until the first paint (SetTransparent) did not remove it: the window is put on screen before GTK paints into it.
- Bottom strip blinks on every property switch. For one frame, the Rotation row and the Log caption are replaced by blank grey while wxAuiManager::Update() re-lays the panes out. Freezing the frame during the update (as BuilderRedrawHold does on Windows) made it a black blink instead and was reverted.
Both are probably the same cause: with GTK frame sync off under XWayland (needed so dialogs repaint), intermediate states reach the screen. Possible directions: re-lay out only when the layout really changes (a property switch in list + detail mode need not run a full Update()); for the floating window, create it once and keep it, or dock the MO Diagram instead of floating it.
- Dominant language
- C
- Stars
- 10
- Forks
- 8
- Avg merge
- 21m
- Merged PRs (30d)
- 1
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from FriendsofECCE/ECCE
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
FriendsofECCE/ECCE#336 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
FriendsofECCE/ECCE#359 ·
-
Difficulty 5/5 Over a week Newbie friendliness 28/100
FriendsofECCE/ECCE#358 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
FriendsofECCE/ECCE#357 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
FriendsofECCE/ECCE#356 · 1 comment ·
All issues in FriendsofECCE/ECCE
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
AFLplusplus/AFLplusplus#2903 ·
-
category:port-update
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
colbymchenry/codegraph#2634 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 8 days