Xingyu Ni

Thanks. I will provide a reproduceable code snippet here. The screen recording on my computer is also attached. ```C++ #include #include #include #include int main(void) { GLFWwindow* window; glfwInit(); NFD_Init();...

Sure. It turns out that "Success!" or "User pressed cancel." or "Error: ..." can be successfully written, and the thread ID is always the same. I am afraid that the...

It was 'success'. It seems that besides the non-blocking issue, every thing is correct. OK, I will study on these projects.

@btzy Dear maintainer, I have looked into `nfd_win.cpp` and got to the root of the problem. In Line 375, 446, and 515, the code calls the member function `Show(hwndOwner)` of...

I think that this is because the Windows API simply calls Window kernel functions. Although API itself is run on the main thread of the user process, if not specified,...

I printed the thread IDs as follows: ```C++ #include #include #include #include #include #include #include int main(void) { GLFWwindow* window; glfwInit(); NFD_Init(); window = glfwCreateWindow(640, 480, "Hello World", NULL, NULL);...

Code snippet: ```C++ #include #include #include #include #include #include #include #include int main(void) { GLFWwindow* window; glfwInit(); NFD_Init(); window = glfwCreateWindow(640, 480, "Hello World", NULL, NULL); glfwMakeContextCurrent(window); glfwSetMouseButtonCallback(window, [](GLFWwindow *window,...