-
-
Notifications
You must be signed in to change notification settings - Fork 10.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Floating-point issues rendering tables with over 500k rows #4779
Comments
This is a duplicate of #3962 #3609 and also ocornut/imgui_club#20 |
Ah sorry, I missed these. Thank you! |
There are multiple sides to this issue but I think if you provide a height to |
Interesting! That does seem to make it quite a lot better so far from what I can see. Thank you for the tip! |
I've pushed improvements for this now, see #3609 |
Amazing, thanks again! |
Version/Branch of Dear ImGui:
Version: 1.85
Branch: master
Back-end/Renderer/Compiler/OS
Back-ends: imgui_impl_dx11.cpp + imgui_impl_win32.cpp (or specify if using a custom engine/back-end)
Compiler: Visual Studio 2019
Operating System: Windows 10
My Issue/Question:
When I render a table with more than about 550k rows, I start noticing some artifacts on the scrolling behavior.
I assume these are both the same issue that coordinates are represented using float instead of double, so there is a loss of precision.
Do you think this is something that could be fixed in an upcoming release of Dear ImGui? Otherwise, what workaround might you suggest here? Maybe I make a fork and change all the coordinates to double instead of float?
I'm trying to develop a viewer for data entries where there could be millions of records, and the user can smoothly scroll through the list, and as the user scrolls, we fetch the appropriate entries to render. Getting this to work with ImGui has been a great experience - thank you for all your hard work developing this amazing library! If I could get the scrolling working smoothly for large tables, this would be a perfect solution for what I'm trying to build.
Screenshots/Video
Standalone, minimal, complete and verifiable example: (see #2261)
The text was updated successfully, but these errors were encountered: