You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, a lot of the API accepts ImFloat or float[] and the cooresponding types. It does this so ImGui can have a setter and a getter to that variable. However, the ImFloat, etc. are implemented as final class. It would be more convenient if the ImGui API instead accepted an interface instead, with get, set, etc. such that one could wrap existing variables with ImGui widgets. I believe this is frequently done in the C++ version and one of the best ways to use ImGui.
@SpaiR what do you think about this? For now I will just sync manually before and after the ImGui calls.
The text was updated successfully, but these errors were encountered:
Currently, a lot of the API accepts ImFloat or float[] and the cooresponding types. It does this so ImGui can have a setter and a getter to that variable. However, the ImFloat, etc. are implemented as final class. It would be more convenient if the ImGui API instead accepted an interface instead, with get, set, etc. such that one could wrap existing variables with ImGui widgets. I believe this is frequently done in the C++ version and one of the best ways to use ImGui.
@SpaiR what do you think about this? For now I will just sync manually before and after the ImGui calls.
The text was updated successfully, but these errors were encountered: