lapce / lapce/floem

Examples do not paint the UIs on startup.

Open
#166 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

S: help wanted T: bug
Dominant language
Rust
Stars
4.3k
Forks
218
PR merge metrics
No merged PRs in 30d

Description

Have just discovered Floem (via This Week in Rust) and have been looking at the examples.

Problem:
None of the examples paint their UIs upon startup (at least on my system).
The winit window frame is displayed but the window content is just whatever was on screen behind the window when it opened.
The only action that triggers the UI to start painting itself is resizing the window.
Via the Counter example I can observe that I can click on the buttons that are not visible (the console reports when the counter is reset). These application state changes do not trigger the UI to paint itself.
Once the window has been resized to trigger the first paint of the UI the examples work as intended.

Environment
rustc: 1.73.0 - stable-x86_64-unknown-linux-gnu
Operating System: Arch Linux
KDE Plasma Version: 5.27.9
Kernel Version: 6.6.1-arch1-1 (64-bit)
Graphics Platform: X11
Graphics Processor: NVIDIA GeForce GTX 1080

Please let know what else I can do to assist solving this problem.

Thanks.

Contributor guide

Open the contributing guide

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.

Research direction

Start by running the Floem examples in the reported Rust, Arch Linux, KDE Plasma, X11, and NVIDIA environment and reproduce the blank window until resize. Trace the initial paint path and verify that the examples render their UI on startup and respond to state changes without requiring a resize.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.