Alexander Neumann

Please add yourself to the AUTHORS file.

There's a lot: http://msdn.microsoft.com/en-us/library/windows/desktop/hh447209(v=vs.85).aspx ;-p

You need a manifest file: https://github.com/lxn/walk#create-manifest-testmanifest https://github.com/lxn/walk#application-manifest-files

This indeed isn't supported. The main obstacle is to get at the name of the primary key sequence.

Yes, returning is nice, but to implement LastInsertId, how would we know the exact name of the id column without guessing?

You can do it like this, too: ```Go err := MainWindow{ AssignTo: &mainWin, Title: "MainWindow", Icon: "foo.ico", (snip) }.Create() ```

You probably are looking at the docs at golang.org, which happen to be for Linux. For Windows, the signature is ```Go func Syscall(trap, nargs, a1, a2, a3 uintptr) (r1, r2...

I have seen my walk apps crashing randomly like this, but haven't been able to find the cause.

Honestly, I'm not sure. Some time ago, I had commented out the call to `runtime.LockOSThread` and tried running applications that use win + walk packages. I didn't notice any issue,...

It looks like you do not initialize `LoginDialog.remembermeCheck`, which you access in `LoginDialog.onLoginButtonClicked`. In `newLoginDialog` only the local variable `remembermeCheck` is initialized.