inkeliz
inkeliz
Disabling the `glfw.AutoIconify` fix that: ``` glfw.WindowHint(glfw.AutoIconify, 0) ``` However, it also prevent from minimize the window.
I have the same issue, I'm trying to cross-compile from Windows to Linux. :\ ``` # github.com/sciter-sdk/go-sciter ..\..\sciter-sdk\go-sciter\types_string.go:27:9: undefined: BehaviorEvent ..\..\sciter-sdk\go-sciter\types_string.go:62:9: undefined: MouseEvent ..\..\sciter-sdk\go-sciter\types_string.go:78:9: undefined: CursorType ..\..\sciter-sdk\go-sciter\types_string.go:89:9: undefined: KeyEvent ..\..\sciter-sdk\go-sciter\types_string.go:100:9:...
It doesn't work, not using the `-DSTATIC_LIB`, it returns: ``` sciter-x-api.c: In function 'SAPI': sciter-x-api.c:15:20: error: expected expression before ':' token tiscript::ni( _api->TIScriptAPI() ); ``` https://github.com/sciter-sdk/go-sciter/blob/master/sciter-x-api.c#L15
Well, it fix the problem, but I think have another error. :'( In my case it returns some warnings: ``` sciter-x-api.c: In function 'SAPI': sciter-x-api.c:14:34: error: 'nullptr' undeclared (first use...
Well, one error was remove, but seems one continue, with more explanation: ``` # github.com/sciter-sdk/go-sciter C:\Users\Inkeliz\AppData\Local\Temp\go-build523114306\b126\_x007.o: In function `SAPI': ..\..\sciter-sdk\go-sciter/sciter-x-api.c:18: undefined reference to `SciterAPI' ..\..\sciter-sdk\go-sciter/sciter-x-api.c:18: undefined reference to `SciterAPI' ..\..\sciter-sdk\go-sciter/sciter-x-api.c:18:...
Finally, I could compile the Sciter and gets the lib. But using the same command mentioned by @pravic it returns: ``` # runtime/cgo gcc: error: "-lsciter-win-64: Invalid argument ```
Yes. So, that is impossible? :\ Can I compile the lib with GCC, or something compatible?
My knowledge about GCC, and Microsoft Visual C++, is close to zero. Do you think that is possible to compile using GCC on Windows? If I compile using linux, can...
I'm using the MinGW, which is mentioned on [README](https://github.com/sciter-sdk/go-sciter#getting-started). To be precise, I'm using "x86_64-w64-mingw32 6.3.0". I'll take a look on that. But, I'm closer to give up about this...
Hi, It's due hard-forks published by NF. The lastest version drops the UDP support, also releases new Epoch-Blocks. Futhermore, there's new breaking-changes (changes that aren't backward compatible) planned (https://forum.nano.org/t/new-state-block-design/892), but...