M.Sz.
or even better: ```txt . └── pkg ├── backend │ └── glfw └── cimgui ``` This way, go will not grab (iirc) glfw if it is not imported, it will...
yah, and (if something unexpected happens) can fork the upstream and use it with `go mod edit -replace`
oh no, so we need to revert the other PR as well?! **EDIT** I mean #40
> @gucio321 yes well... let's go ahead and do it
> Who is the lib user? on long term i would suggest, both, > > (A) the one who just need to create a quick simple tool for easy tasks,...
also, I'm just looking at this and I'm not sure if cimgui-go actually uses backend somehow. As far as I see it is only used by examples and is mostly...
@AllenDang we should deffinitely switch to go-gl/glfw because: - we shouldn't focus on binding - there is a dedicated team for this - if we have some idea how to...
Yes and no. Currently we our custom glfw wrapper. Can't we just use this one from go-gl? An use imgui_impl_glfw to go imgui things... (Ifk if its gonna eork, what...
It's most likely not issue for us: I've checked imgui example for glfw recently and it does the same
@Wolf65 are you able to do this on c++ imgui's glfw example?