client and server on Linux

[hinxx]

My embedded system (no keyboard/screen) processes data and I'm considering using netImgui to move that data to the PC (keyboard/screen) and use ImGui to visualize it and interact with the embedded system. They would both be Linux based and have opengl3 and glfw.

I'm little confused on what part of netImgui runs where and how it is referred to in the docs / code / comments. Would the server run on the embedded system and the client on the PC in my case, or is it the other way around?

Which ImGui render/input backend should the embedded system use?

Reading through some older issues I get a feeling that Linux support is there but not complete. Has that changed?

Can you point me to an existing sample code that would best fit the use case outlined above, please?

Thank you in advance!

[sammyfreg]

The embedded system is the client and does not need any rendering backend! I actually have a sample demonstrating using ImGui on a console client without any rendering needed on it. The Server application is the NetimguiServer program that you can find in the depot. Since I didn't have a Linux setup, I never fully ported it to that platform. However, it already supports OpenGL and the platform specific code is clearly separated in a few functions (prefixed with 'HAL') so it shouldn't require too much efforts to finish support. Note: even if your embedded system is using Linux, it can connect without issue to the NetImguiServer application running on Windows.

…

On Thu., Oct. 27, 2022, 19:02 hinxx ***@***.***> wrote: My embedded system (no keyboard/screen) processes data and I'm considering using netImgui to move that data to the PC (keyboard/screen) and use ImGui to visualize it and interact with the embedded system. They would both be Linux based and have opengl3 and glfw. I'm little confused on what part of netImgui runs where and how it is referred to in the docs / code / comments. Would the server run on the embedded system and the client on the PC in my case, or is it the other way around? Which ImGui render/input backend should the embedded system use? Reading through some older issues I get a feeling that Linux support is there but not complete. Has that changed? Can you point me to an existing sample code that would best fit the use case outlined above, please? Thank you in advance! — Reply to this email directly, view it on GitHub <#39>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AESBPY67LNZNYK3NY424RHDWFJHLXANCNFSM6AAAAAARP4EACA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[hinxx]

Thanks for clarifying!

I'm using g++ on Linux platform.
I've compiled the SampleNoBackend as the client with no issues.

Now I'm trying to compile the ServerApp as well and I'm facing this error:

g++ -std=c++11 -I../../ThirdParty/DearImgui -I../../ThirdParty/DearImgui/backends -g -Wall -Wformat -I. -I../../ -I../../Client `pkg-config --cflags glfw3` -c -o NetImguiServer_RemoteClient.o NetImguiServer_RemoteClient.cpp
NetImguiServer_RemoteClient.cpp: In member function ‘NetImguiServer::RemoteClient::NetImguiImDrawData* NetImguiServer::RemoteClient::Client::GetImguiDrawData(void*)’:
NetImguiServer_RemoteClient.cpp:241:83: error: invalid conversion from ‘uint64_t’ {aka ‘long unsigned int’} to ‘ImTextureID’ {aka ‘void*’} [-fpermissive]
  241 |     pCmdList->CmdBuffer[drawIdx].TextureId = NetImgui::Internal::TextureCastHelper(pEmtpyTextureHAL); // Default to empty texture
      |                                              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~
      |                                                                                   |
      |                                                                                   uint64_t {aka long unsigned int}
NetImguiServer_RemoteClient.cpp:246:85: error: invalid conversion from ‘uint64_t’ {aka ‘long unsigned int’} to ‘ImTextureID’ {aka ‘void*’} [-fpermissive]
  246 |       pCmdList->CmdBuffer[drawIdx].TextureId = NetImgui::Internal::TextureCastHelper(mvTextures[texIdx].mpHAL_Texture);
      |                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      |                                                                                     |
      |                                                                                     uint64_t {aka long unsigned int}

Should I just cast the return value to ImTextureID?

BTW, I had to comment out this line #include "backends/imgui_impl_win32.cpp" from NetImguiServer_App_GlfwGL3.cpp..

[hinxx]

Should I just cast the return value to ImTextureID?

Did that and it compiled fine.

I managed to also run the server and client on the same Linux host!

This looks very cool!

[sammyfreg]

Nice! I never tried it on Linux before. For the imtexture cast issue, I already have a utility that handle the casting, probably hasn't been replaced to use it yet in the GL code. You can look for 'TextureCastHelper'.

…

On Thu., Oct. 27, 2022, 21:54 hinxx ***@***.***> wrote: Should I just cast the return value to ImTextureID? Did that and it compiled fine. I managed to also run the server and client on the same Linux host! [image: Screenshot_2022-10-27_14-51-45] <https://user-images.githubusercontent.com/2725009/198289485-81eb4719-a77f-44af-a76d-8d2b82a18fc1.png> This looks very cool! — Reply to this email directly, view it on GitHub <#39 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AESBPY2JDSAUU5RXO2IBBVLWFJ3OZANCNFSM6AAAAAARP4EACA> . You are receiving this because you commented.Message ID: ***@***.***>

[hinxx]

That code seems to be already using the TextureCastHelper. Looks like it is picking up the wrong one, though. If I explicitly cast the argument to (const void*) then the compiler is happy.

Here the little diff that sorts that out:

$ git diff NetImguiServer_RemoteClient.cpp
diff --git a/Code/ServerApp/Source/NetImguiServer_RemoteClient.cpp b/Code/ServerApp/Source/NetImguiServer_RemoteClient.cpp
index 2046ec9..7a08103 100644
--- a/Code/ServerApp/Source/NetImguiServer_RemoteClient.cpp
+++ b/Code/ServerApp/Source/NetImguiServer_RemoteClient.cpp
@@ -238,12 +238,12 @@ NetImguiImDrawData*       Client::GetImguiDrawData(void* pEmtpyTextureHAL)
                        for(int drawIdx(0), drawCount(pCmdList->CmdBuffer.size()); drawIdx<drawCount; ++drawIdx)
                        {
                                uint64_t wantedTexID                                    = NetImgui::Internal::TextureCastHelper(pCmdList->CmdBuffer[drawIdx].TextureId);
-                               pCmdList->CmdBuffer[drawIdx].TextureId  = NetImgui::Internal::TextureCastHelper(pEmtpyTextureHAL); // Default to empty texture
+                               pCmdList->CmdBuffer[drawIdx].TextureId  = NetImgui::Internal::TextureCastHelper((const void*)pEmtpyTextureHAL); // Default to empty texture
                                for(size_t texIdx=0; texIdx<clientTexCount; ++texIdx)
                                {
                                        if( mvTextures[texIdx].mImguiId == wantedTexID )
                                        {
-                                               pCmdList->CmdBuffer[drawIdx].TextureId  = NetImgui::Internal::TextureCastHelper(mvTextures[texIdx].mpHAL_Texture);
+                                               pCmdList->CmdBuffer[drawIdx].TextureId  = NetImgui::Internal::TextureCastHelper((const void*)mvTextures[texIdx].mpHAL_Texture);
                                                break;
                                        }
                                }

[sammyfreg]

Thank you for your investigations, c707101 should fixes them. Let me know if there's still some problems.