Question about the Quit menu #4797
Unanswered
halsten-dev
asked this question in
Q&A
Replies: 1 comment 2 replies
-
Quit shortcuts should be handled by the operating system. Calling App.Quit should not panic though, sounds like maybe you should open a bug to report this. (Though a nil error more likely means you don't actually have access to the app when you called Quit, but on a nil variable instead?) |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I started using the menu and it's working fine. It's a bit sad to be forced to register the shortcut on the canvas too to make the shortcuts work, but it works so that's ok.
The question is about the Quit menu item that is automatically added. Sadly it seems not very possible to modify it to add a shortcut or even making my own do not work. When I call
app.Quit()
from a shortcut I get this kind of error :panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x58 pc=0xa09b7c]
Does anyone have achieved something like that ?
Thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions