vinser

IMO it works as expected for double-barrelled names. https://en.wikipedia.org/wiki/Double-barrelled_name

I get the same result when using in package assets/image.jpg

Significantly simplified the test example. It doesn't need a test sample. But this error occurs much less frequently with it. You have to start the dialog multiple times. ```go package...

Maybe the dialogue just doesn't have enough time to render. If after dialog.Show() you put some code with a delay, ```go s := w.Content().Size() w.Resize(s.AddWidthHeight(-1, -1)) time.Sleep(10 * time.Millisecond) w.Resize(s)...

This does not depend on the OS and hardware. I have the same bug on my Intel NUC with Windows 10

Maybe this issue is induced by high CPU load. Screenshot for above code load  **It is like #4574**

Thank you for the info about go problems with ldflags on some platforms but on linux and windows desktop OSes it works. I've used -ldflags in my other not fyne...

In fyne-cross sources I found such a test case: ```go { name: "custom ldflags", args: args{ flags: &CommonFlags{ AppBuild: 1, Ldflags: "-X main.version=1.2.3", }, }, want: Context{ AppBuild: "1", AppID:...

`GOFLAGS="-ldflags=-X -ldflags=main.version=0.0.1" fyne-cross linux` makes the same bug result

The syntax you describe above `fyne-cross linux -ldflags=-X=main.version=0.0.1` does not work too - main.version is not initialized. Concerning -release option with -ldflags I think it's because fyne has no -ldflags...