Closed 173619070 closed 1 year ago
what other resource? another VkSurfaceKHR sounds good, if you are using the same physical device and graphic queue, a single VkvgDevice could output to vulkan image from both. Vkvg is basically to draw on vulkan texture, it does not handle the windowing system, you need some kind of window manager (like glfw) for that. If you make a nice example with glfw and multiple window, I can add it to the repo.
what other resource? another VkSurfaceKHR sounds good, if you are using the same physical device and graphic queue, a single VkvgDevice could output to vulkan image from both. Vkvg is basically to draw on vulkan texture, it does not handle the windowing system, you need some kind of window manager (like glfw) for that. If you make a nice example with glfw and multiple window, I can add it to the repo.
i may not have expressed clearly,what I mean is that in multi-window mode those resources are shared by windows, and those resources are exclusive to windows,are you distinguishing in your code,I think a better way is to develop based on windows,2D applications typically have multiple windows.
I'm sorry but my time is a bit short, feel free to come back to me with concrete examples and materials. What could be of interest, is analyzing workflow with multiple devices, but that's an higher stack, not really in the scope of this library. I'm also interested in kms (https://github.com/nyorain/kms-vulkan)....
i want to use it in multiple window,so what can i do? should i create another VkSurfaceKHR object ?what about another resource?