[Windows] Verify: flashes and blank frames on start, show, restore and maximize
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Start with a Flutter app using the Window API and reproduce each of the eight linked Windows reports against nativeapi 0.6.0. Check startup, show, restore, maximize, positioning, and repaint behavior, including the runner's first-frame Show() race. Done means each checklist item is marked as reproduced and fixed or documented as no longer occurring.
Written by the indexing model from the issue text.
Description
These were reported against window_manager 0.5.x, whose platform code is gone: window_manager 0.6.0 is rebuilt on nativeapi. None of them has been checked against nativeapi yet. Each needs a reproduction with nativeapi (a Flutter app on the Window API), then a fix or a note that it no longer happens. Tick them off here as they're checked.
- leanflutter/window_manager#153: black background flashes when restoring from maximized
- leanflutter/window_manager#155: white screen for up to seconds when showing after hide()
- leanflutter/window_manager#383: white screen after maximize()
- leanflutter/window_manager#428: white flash on startup before the background colour applies
- leanflutter/window_manager#504: window flashes at another position before moving to the centre on startup
- leanflutter/window_manager#578: part of a window dragged back from off-screen isn't repainted in time
- leanflutter/window_manager#412: maximize() at startup reverts to the default size (runner's first-frame
Show()races with it) - leanflutter/window_manager#223 / leanflutter/window_manager#572: position or maximize the main window before it first appears, without a visible jump
- 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
- 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 libnativeapi/nativeapi
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
libnativeapi/nativeapi#81 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
libnativeapi/nativeapi#80 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
libnativeapi/nativeapi#79 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
libnativeapi/nativeapi#78 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
libnativeapi/nativeapi#77 ·
All issues in libnativeapi/nativeapi
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
objectionary/eo-graphs#74 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 88/100
QuantStack/git2cpp#187 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100