Running examples/hello resulted in error.

[jerry9723988]

I cloned the repository and ran hello, but encountered the following problems:

1. The internal interface only refills the window after I release the mouse button when resizing it.

2. The interface displays incorrectly, as shown in the image below.

3. The mouse click coordinates are incorrect.

4. The font is blurry.

5. Scrolling is incorrect; only the incorrect portion of the scrolling is displayed.

My computer is a Mac Pro M1.

go.mod :

module github.com/gogpu/ui/examples/hello

go 1.25.0

replace github.com/gogpu/ui => ../..

require (
github.com/gogpu/gg v0.48.7
github.com/gogpu/gogpu v0.41.0
github.com/gogpu/ui v0.1.29
)

require (
github.com/coregx/signals v0.1.0 // indirect
github.com/go-text/typesetting v0.3.4 // indirect
github.com/go-webgpu/goffi v0.5.3 // indirect
github.com/go-webgpu/webgpu v0.5.2 // indirect
github.com/gogpu/gpucontext v0.19.0 // indirect
github.com/gogpu/gputypes v0.5.0 // indirect
github.com/gogpu/naga v0.17.13 // indirect
github.com/gogpu/wgpu v0.29.1 // indirect
golang.org/x/image v0.41.0 // indirect
golang.org/x/sys v0.45.0 // indirect
golang.org/x/text v0.37.0 // indirect
)

[kolkov]

Hi @jerry9723988, thanks for the detailed report!

The symptoms you're describing — incorrect display, offset mouse coordinates, blurry fonts, broken scrolling — are all consistent with a HiDPI/Retina scaling mismatch. We've recently opened a deep investigation into HiDPI handling across the ecosystem in gogpu/gogpu#306.

Your Mac M1 has a Retina display (2x scale factor), and the screenshot resolution (2244×1878) confirms the window is rendering at physical pixel dimensions. The root cause is likely the same class of issue — scale factor not being applied consistently through the rendering pipeline.

Could you try updating to the latest versions? Your go.mod shows gogpu v0.41.0, but we've since released v0.41.10 with several fixes. Try:

go get github.com/gogpu/gogpu@latest
go get github.com/gogpu/gg@latest
go get github.com/gogpu/ui@latest
go mod tidy

If the issue persists on latest versions, could you share the console output? There should be a line like:

ggcanvas.NewWithScale logical_w=... logical_h=... scale=... physical_w=... physical_h=...

This will tell us whether the scale factor is being detected correctly.

We're actively investigating and tracking this in gogpu/gogpu#306. Will update here when we have a fix.

[jerry9723988]

I have updated gogpu to the latest version:

github.com/gogpu/gogpu v0.41.12

The same problem persists. Running go run . only produces one line of console output.

I get 1 when I retrieve the ScaleFactor before desktop.Run:

    uiApp.SetRoot(buildUI(m3))
    scale := gogpuApp.ScaleFactor()
    fmt.Printf("scale factor: %f\n", scale)

    if err := desktop.Run(gogpuApp, uiApp); err != nil {
        log.Fatal(err)
    }

Getting ScaleFactor in the ListView's OnItemClick method gives 2

    listview.OnItemClick(func(index int) {
    scale := gogpuApp.ScaleFactor()
    fmt.Printf("scale factor: %f\n", scale)
    fmt.Printf("clicked: %s\n", items[index])
})

Please forgive me, I'm not very familiar with Go and cannot pinpoint a more precise location.

[porjo]

@jerry9723988 there have been a lot of fixes in recent version. I'd recommend to try again with latest version.

[kolkov]

A lot has changed since your last test (gogpu v0.41.12 → v0.44.11, wgpu v0.30.23, gg v0.50.8). Could you re-test with the latest release (v0.1.47)? The Metal backend has received several fixes since then, including MSAA storage mode for Intel integrated GPUs (wgpu#271).