-
-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem with dialogs #289
Comments
I'll look into it in later |
After more tests: it does not depend on glib/gdk thread-awareness, tested with and without them. |
Hmm, I don't reproduce this as your said. I need to make development-environment for gtk. |
Done more tests: demo app works fine, I can see file selection dialog, and no crash. Also, if I remove dialog - application continue to work flawlessly. Also, simple app: package main
import (
"github.com/mattn/go-gtk/gtk"
)
func main() {
gtk.Init(nil)
m := gtk.NewMessageDialog(nil, gtk.DIALOG_MODAL, gtk.MESSAGE_INFO, gtk.BUTTONS_OK, "Test")
m.Response(func() {
m.Destroy()
})
m.Run()
gtk.Main()
} Also shows dialog fine. |
This is tested on Linux? |
Yes, on Centos 7 and Ubuntu 14.04, sorry for not mentioning it. |
NP. Then still have issue? |
Yep, I have to disable MessageDialog generation on Linuxes in URTrator to get around it. :( https://github.com/pztrn/urtrator/tree/6495e9073704ce0658d63a6692b810f7e0807a8c is a last commit before I workarounded this bug (or my bad hands?). |
Should be a bug of go-gtk. |
I tried your code on Ubuntu 16.04 (clean installed) and go1.7.3. But can't reproduce. |
Hello.
Trying to run urtrator (https://github.com/pztrn/urtrator) on fully updated CentOS 7. Everything builds and run fine, except dialogs. When I'm trying to show dialog (e.g. https://github.com/pztrn/urtrator/blob/master/ui/options.go#L70) this errors appeared:
Also, I've tested on Debian 8 (fully updated) - and very same error :(. So I doubt that this related to OS or GTK+2 build.
Also, macOS and Windows (7 and 2012r2) are fine, dialog shows normally.
The text was updated successfully, but these errors were encountered: